This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: relocating the compiler and associated tools


On Tue, 9 Nov 2004, Dan Kegel wrote:

> Robert P. J. Day wrote:
> > On Tue, 9 Nov 2004, Arno Schuring wrote:
> >
> >
> > > [target-]gcc --print-file-name crt1.o
> >
> >
> > $ gcc --print-file-name crt1.o
> > /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../crt1.o
> >
> >
> > > [target-]gcc --print-file-name specs
> >
> >
> > $ gcc --print-file-name specs
> > /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs
> >
> >   that's using the *native* gcc on my FC2 system, on the files in the
> > *copied* lib/gcc/... directory.  was that the combination you wanted
> > me to test?
>
> No.  He wanted you to use sh3-linux-gcc, the compiler you just built
> and relocated, to see where it was looking for its data files.  If
> it replies with old hardcoded paths, that's a warning sign that
> the relocation didn't completely take.

ok, here we go.  with the files crt1.o and specs in the *copied*
directory under /usr/local, we have:

$ /usr/local/sh3/bin/sh3-unknown-linux-gnu-gcc --print-file-name
crt1.o
/usr/local/sh3/bin/../lib/gcc/sh3-unknown-linux-gnu/3.4.1/../../../../sh3-unknown-linux-gnu/lib/crt1.o

$ /usr/local/sh3/bin/sh3-unknown-linux-gnu-gcc --print-file-name specs
/usr/local/sh3/bin/../lib/gcc/sh3-unknown-linux-gnu/3.4.1/specs


  in other words, it looks good, no?

rday

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


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