This is the mail archive of the crossgcc@sourceware.org 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: linking correct libc


Yann, anyone? Can't anyone see what is going wrong with the crosstool ld here?

I have just compiled gnuplot (an automake ./configure project) and had to reinstate the symlink in sys-tools: libc.so.6 -> libc-2.9.so , so everything seems to be fine here.

Clearly it is searching the correct directories and NOT in the host's /lib .

So why is it ONLY searching the host's /lib/libc.so.6 when I try to link portmap?


Portmap is probably the smallest project I've had to work on but this one damn problem has been holding me back for nearly 2 weeks now.


It seems that in interpreting the contents of the arm build's libc.so it is taking the reference to /lib/libc.so.6 literally and not in the context of a cross-compilation.

What can be making this happen?

regards, Peter.


-- For unsubscribe information see http://sourceware.org/lists.html#faq


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