We are having some problems building e2fsprogs using our custom distro
based on poky-tiny.
The error we get is typically:
e4defrag.c:1958: undefined reference to `nftw64'
So, it seems some libc feature in addition is missing to get proper
working support for the large file API.
Below is a comparison between standard poky and our distro.
poky:
DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia
usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 ipv4 ipv6
libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets
libc-charsets libc-crypt libc-crypt-ufc libc-db-aliases libc-envz
libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse libc-getlogin libc-idn
libc-inet-anl libc-libm libc-libm-big libc-locales libc-locale-code
libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug
libc-spawn libc-streams libc-sunrpc libc-utmp libc-utmpx libc-wordexp
libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc
libc-posix-wchar-io largefile opengl multiarch wayland pulseaudio
sysvinit"
poky-custom (based on tiny)
DISTRO_FEATURES="ipv4 usbhost usbgadget ${DISTRO_FEATURES_WIFI}
libc-libm libc-crypt libc-utmp libc-getlogin libc-posix-regexp
libc-inet libc-nis libc-posix-clang-wchar libc-posix-wchar-io
libc-locale-code sysvinit largefile nfs"
A huge difference indeed, which is sort of the whole point ;) Anyone
have the slightest idea what of the libc features we need to enable
additionally to get full large file support?
A trial and error approach playing a guess game to figure this out
would become a very tedious task :( It is probably obvious once
it/they are identified but right now it is complete darkness.
Thanks.
Hans
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
