This is the mail archive of the binutils@sources.redhat.com 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: PATCH: Add LIBPATH_SUFFIX for ${tool_lib}.


On Thu, Aug 14, 2003 at 10:20:20AM +0930, Alan Modra wrote:
> On Wed, Aug 13, 2003 at 05:20:02PM -0700, H. J. Lu wrote:
> > On Thu, Aug 14, 2003 at 09:37:02AM +0930, Alan Modra wrote:
> > > On Wed, Aug 13, 2003 at 03:52:42PM -0700, H. J. Lu wrote:
> > > > We didn't add LIBPATH_SUFFIX for ${tool_lib}. As the result, we got
> > > > 
> > > > SEARCH_DIR("/export/tools/ppc64-linux/lib");
> > > > 
> > > > This patch changed it to
> > > > 
> > > > SEARCH_DIR("/export/tools/ppc64-linux/lib64"); SEARCH_DIR("/export/tools/ppc64-linux/lib");
> > > 
> > > I think this would be wrong.  By adding a /lib64 version of
> > > ${tooldir}/lib you seem to be inferring that ${tooldir}/lib is now for
> > > 32 bit libraries.
> > 
> > Isn't that true? When you configure binutils with
> > 
> > ..../configure --target=ppc64-linux --prefix=/export/tools
> > 
> > where are 32 bit libraries? where are 64bit libraries?
> 
> In /export/tools/lib, /export/tools/lib64 and so on.  ie. in the normal
> system lib dirs.

I thought /export/tools/lib was for host, not target. The current
cross linker won't even look at /export/tools/lib.

> 
> I'm very nervous about changing the meaning of ${tooldir}/lib without
> some serious thought as to the consequences.  Also, to achieve anything,
> you'll need to change a whole lot of other tools, eg. gcc, that know
> that $prefix/$target/* contain headers and libs for $target.

How does one setup a 32/64 bit cross compiler?


H.J.


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