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]

not really crossgcc


Hi folks,

I have used Dan's crosstool (and I can't begin to describe
how much time and grief it has saved me) to build the toolchain
for HOST=yellowdoglinux, TARGET=almost-the-same-as-host.
That's right, it's sort of a "cross" build, but also not, sort of.

Now I want to "install" it on another host in some nice place
like /usr/local, so I don't overwrite the tools already there.
Build a simple executable, say hello-world, with the new tools,
and run it on the host.  I have finally arrived at my problem.

At runtime, the program uses /lib/ld.so.1 to load /lib/libc.so.6,
the host's tools.  How can I "configure" my tools to look only
in /usr/local/lib/ for these things?  I can force it to use my
libc with
	-Xl,-rpath,/usr/local/lib
and to use my ld.so.1 with
	-Xl,-I,/usr/local/lib/ld.so.1

Are these the right way to do it?  How can I make them implicit
so my users don't have to specify them?  Thanks.

Mike LeBlanc


------ 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]