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]

How to point to new gcc libs (instead of default gcc)


Hi,

I used crostool-ng 1.5.2 to build a toolchain for x86-32 (linux
2.6.27.35, gcc 4.3.2, glibc 2.9)

I used the -L switch to point to the path of the libs created with the
toolchain (/opt/toolchain/i686-nptl-linux-gnu/sys-root/usr/lib)

But when I did: ldd my_app.out I got:

 ldd my_app.out
        linux-gate.so.1 =>  (0x00f61000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0074d000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x03653000)
        librt.so.1 => /lib/librt.so.1 (0x0077c000)
        libc.so.6 => /lib/libc.so.6 (0x005d6000)
        /lib/ld-linux.so.2 (0x005b3000)
        libm.so.6 => /lib/libm.so.6 (0x0071e000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0059e000)

It seems that the out file is linked dynamically against the list is
/usr/lib and not "my" libs.
Can I fix it with a gcc switch ?

Thanks.

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