Hi,
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?
Cheers,
MH
Am 05.05.2011 11:02, schrieb Bernhard Reutner-Fischer:
On 5 May 2011 10:41, Matthias Hofmann<[email protected]> wrote:
Hi,
i am not sure if this is a bug, i guess, there are some features missing in
my config-file or it is generally not supported by uclibc.
You should fix that app.
# UCLIBC_SUSV3_LEGACY is not set
ftime was marked for removal in SUSv3 about 7 years ago and was
removed since then.
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.
HTH,
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc
