> -----Original Message-----
> From: ANDY KENNEDY [mailto:[email protected]]
> Sent: Friday, March 11, 2011 7:12 PM
> To: Filippo ARCIDIACONO; Carmelo AMOROSO
> Cc: [email protected]
> Subject: RE: Strange: MIPS, librt, malloc (Cross Post:
> originally senttoBuildroot -- oops).
>
> >
> > Hi Andy,
> > I run your test in my sh4 target and it works fine, w/o link librt.
>
> Um, did you do it both ways?
Yes. Here the tests output I got:
# ./test-rt
Hello world
# ldd ./test-rt
librt.so.0 => /lib/librt.so.0 (0x2956f000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x29582000)
libc.so.0 => /lib/libc.so.0 (0x2959d000)
libdl.so.0 => /lib/libdl.so.0 (0x2963b000)
libpthread.so.0 => /lib/libpthread.so.0 (0x2964e000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x29558000)
# ./test-no-rt
Hello world
# ldd ./test-no-rt
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2956f000)
libc.so.0 => /lib/libc.so.0 (0x2958a000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x29558000)
> If I link against librt, hello
> world fails. You are correct, it runs perfectly without it.
> If you did it both ways without failure, then that points to
> mips specific code.
I think so.
>
> > I'm using the latest up-to-date uClibc (commit id
> 1b3f056d4aa2726f872f2ee85f3f391a784e19e4).
> >
> > Regards,
> > Filippo.
>
> Andy
>
Filippo.
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc
