Is it possible to set up uclibc and glibc on one system? I copied the uclibc stuff into the directories which i configured:

#
# Library Installation Options
#
SHARED_LIB_LOADER_PREFIX="$(RUNTIME_PREFIX)lib"
RUNTIME_PREFIX="/usr/uclibc/"
DEVEL_PREFIX="/usr/uclibc/usr/"

but the necessary libs are still not found:

ldd shows:
    linux-gate.so.1 =>  (0x00a74000)
    libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0x00c13000)
    libm.so.0 => not found
    libc.so.0 => not found
    libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0x00f2c000)
    libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0x004f8000)
    libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x0012f000)
    /lib/ld-linux.so.2 (0x00d60000)

which is not correct.
And one last question: There are some 3rd party shared libs (.so) which are built against glibc-2.9 and i do not have the source code of them (closed source). But i need them to run my program and link them to access the symbols. Is there a chance to get the code running if i provide all glibc and uclibc libs?

Thx,
MH

Am 05.05.2011 11:35, schrieb Bernhard Reutner-Fischer:
On 5 May 2011 11:07, Matthias Hofmann<[email protected]>  wrote:
Hi,
please do not top-post.
thanks. I rebuild my toolchain with UCLIBC_SUSV3_LEGACY enabled.
The linking error regarding assert_fail occurs when linking a third party
lib statically into my project. Do i have to rebuild the third party lib
against uclibc or is there an other way?
assert_fail is not available. If your code calls it directly you
should fix it to use the
standard assert(). If it doesn't then you didn't setup your toolchain
properly or try to link
against something not built against uClibc.
You should rebuild the third party lib against uClibc, yes.


--
Matthias Hofmann
Robotics Research Institute
Section Information Technology
TU Dortmund University
44221 Dortmund, Germany
mailto:[email protected]
http://www.it.irf.tu-dortmund.de
Phone: +49 231 755 7008
Fax: +49 231 755 3251

_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc

Reply via email to