use of legacy C library functions

Mike Frysinger vapier at gentoo.org
Mon Apr 5 23:13:36 UTC 2010


On Monday 05 April 2010 14:24:02 Rob Landley wrote:
> I'm testing said release now, since the mips64 target in uClibc 0.9.30.3
> was completely horked (every file saying it was created January 0, 1900). 
> Using uClibc 0.9.31 with the same .config, the static busybox build is
> breaking with:
> 
>   libbb/lib.a(xfuncs.o): In function `close_on_exec_on':
>   xfuncs.c:(.text.close_on_exec_on+0xc): undefined reference to `fcntl64'
>   libbb/lib.a(xfuncs.o): In function `ndelay_off':
>   xfuncs.c:(.text.ndelay_off+0x14): undefined reference to `fcntl64'
>   xfuncs.c:(.text.ndelay_off+0x30): undefined reference to `fcntl64'
>   libbb/lib.a(xfuncs.o): In function `ndelay_on':
>   xfuncs.c:(.text.ndelay_on+0x14): undefined reference to `fcntl64'
>   xfuncs.c:(.text.ndelay_on+0x2c): undefined reference to `fcntl64'
>   loginutils/lib.a(getty.o):getty.c:(.text.getty_main+0x2fc): more
> undefined references to `fcntl64' follow
>   collect2: ld returned 1 exit status
>   make: *** [busybox_unstripped] Error 1
> 
> And I'm trying to figure out if this is a config issue or due to:
> 
>   libc_hidden_def(fcntl64)
> 
> In libc/sysdeps/linux/common/__syscall_fcntl64.c.  (Why "hidden"?  What's
> the point in hiding it?  It's a libc export, right?)

read the documentation in the internal headers.  none of the libc_hidden stuff 
should have any bearing whatsoever on static builds.  nor does "hidden" mean 
what you apparently think it means.

it does seem to be a bug in the uClibc build system though if fcntl64 isnt 
included in libc.a.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20100405/f597e24d/attachment.pgp>


More information about the busybox mailing list