This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add hppa*64* support to libtool in binutils

> > There are some differences between the ia64 implementation and the
> > hppa64 proposed here.  The ia64 defines in look suspect
> > to me.  It seems defines appropriate to the 32-bit SOM linker are
> > being used.
> What defines look suspect to you?  It might just be that it is set up to
> use the HP linker and not the GNU linker.  The GNU linker has not been
> ported to the IA64 HP-UX platform.

This is the code:

    if test $with_gnu_ld = no; then
      case "$host_cpu" in
	  hardcode_shlibpath_var=no ;;
	  hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir' ;;
    hardcode_minus_L=yes # Not in the search PATH, but as the default
			 # location of the library.

I am pretty sure that hardcode_direct should be "no" for ia64 (see  I believe that hardcode_libdir_separator and hardcode_minus_L
do not need to be defined if hardcode_direct is no.  I think
export_dynamic_flag_spec is ignored by the ia64 HP linker (it is by
64-bit hppa linker).  I also think we don't want hardcode_minus_L
with GNU ld.  So, I think a define for hardcode_direct should go
into the ia64 section of the case statement and the other four
should be in the default part.

J. David Anglin                        
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]