Mike Frysinger wrote:
On Saturday 15 July 2006 05:24, Erwan Bracq wrote:
  
If I set LDFLAGS for some specific dirs with -L I'm breaking something
in cross-emerge and it can find the libc.
    

dont add -L to LDFLAGS ... if you need to do this, you're doing it wrong and 
you'll just end up with headaches (i know from personal experience :p)

make sure the libraries can be found via the normal lib search path (ie 
sysroot in /usr/CTARGET)

  
I need to do this because some external libraries are required (and
these libraries are inside the root_filesystem like libcurses.* for bash).
    

the root of your troubles is your mixing of development and target in $ROOT

if you keep things cleanly separated, development headers/libs in /usr/CTARGET 
and target runtime libs in $ROOT, then it should just work
-mike
  

Hi

the root of your troubles is your mixing of development and target in $ROOT

Yes, that's the point, I want to merge development and target due to native compilation possibility (it's a development root filesystem) and I want to keep clear the cross tool dir as much as possible.

I've started to play with rpath ld option and things are not to bad (the libc is now found) but I continue to break on final link with other libraries. I'm trying now to change the ld settings to include more search path (when binutils are emerged)

If I can't get something good with new ld search path, then I will put required libraries in /usr/CTARGET.

Thanks for your help.

R1.

Reply via email to