[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 64bit HPUX problems

From: ross . alexander
Subject: Re: 64bit HPUX problems
Date: Tue, 13 Aug 2002 14:33:40 +0100

This all relates to libtool-1.4e.

I have made changes to config.guess to detect hppa64 systems and
changed in libtool.m4 to add support for for that environment.  However,
I am getting a problem with hardcoded -rpath values.

The 64bit environment has

      hardcode_into_libs = no

but -R /usr/local/lib (for example) picked up in dependency libraries
gets carried though to the $deplibs value used in the link and
relink commands.

This looks like a bug, but could have been fixed in CVS.  If anybody
has come across this, I would like to get it fixed.




Ross Alexander                           "He knows no more about his
MIS - NEC Europe Limited            destiny than a tea leaf knows
Work ph: +44 20 8752 3394         the history of East India Company"

                      Albert Chin                                               
                      <address@hidden        To:       address@hidden           
            >                    cc:       address@hidden   
                                                     Subject:  Re: 64bit HPUX 
                      03/07/2002 16:27                                          
                      Please respond to                                         

On Wed, Jul 03, 2002 at 04:06:16PM +0100, address@hidden
> I don't think we can't really rely on cflags because because the user
> be using gcc, in which
> case we would have to look for __LP64__ (I think).  I think it might be
> easier to check
> $host_cpu for hppa2.0w.  However, a user wanting to build for 32bit would
> then have
> to set the build to hppa2.0n-hp-hpux*.

You can check CFLAGS. If they're using GCC, then have a separate case
statement to handle that:
  case "$CFLAGS" in
    if test "$GCC" = yes; then
    fi ;;

You can also try compiling something and running file/odump/elfdump on
the result to test if the default is a 32/64-bit object file (I
imagine the output should be different for 32/64-bit executables).
I'm leaning towards checking $CFLAGS though.

albert chin (address@hidden)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]