Still no header files; Please at least NAK that it works for you

C Shore alemc.2 at bmts.com
Sat Nov 19 22:42:39 UTC 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, I'm trying to build a uClibc toolchain so that I can prepare a
bootroot disk (which I've done before, but with a much older uClibc).

As I understand it the recommended procedure is to

1) svn co svn://uclibc.org/trunk/buildroot
2) cd buildroot
3) make menuconfig
4) make

This created a file which is an ext2 filesystem.  Good so far.

I uncompress and mount on /mnt

Unfortunately when I look in /mnt/usr/include all I see is:

bash-3.00# ls /usr/include
zconf.h  zlib.h
bash-3.00#

This seems wrong, but maybe I'm missing a step.

I untar uClibc-0.9.28 into /mnt/usr/src/uClibc

I type make menuconfig and get:

make -C extra/config ncurses mconf
make[1]: Entering directory `/usr/src/uClibc-0.9.28/extra/config'
cp zconf.tab.h_shipped zconf.tab.h
gcc -O2 -Wall -DCURSES_LOC="<curses.h>" -I. -c mconf.c -o mconf.o
mconf.c:12:23: sys/ioctl.h: No such file or directory
mconf.c:13:22: sys/wait.h: No such file or directory
mconf.c:14:25: sys/termios.h: No such file or directory
mconf.c:15:19: ctype.h: No such file or directory
mconf.c:16:19: errno.h: No such file or directory
mconf.c:17:19: fcntl.h: No such file or directory
In file included from
/usr/lib/gcc/i386-linux-uclibc/3.4.2/include/syslimits.h:7
,
                 from
/usr/lib/gcc/i386-linux-uclibc/3.4.2/include/limits.h:11,
                 from mconf.c:18:
/usr/lib/gcc/i386-linux-uclibc/3.4.2/include/limits.h:122:61: limits.h:
No such file or directory
mconf.c:19:20: signal.h: No such file or directory
mconf.c:21:20: stdlib.h: No such file or directory
mconf.c:22:20: string.h: No such file or directory
mconf.c:23:21: termios.h: No such file or directory
mconf.c:24:20: unistd.h: No such file or directory
In file included from mconf.c:26:
lxdialog/dialog.h:22:23: sys/types.h: No such file or directory
lxdialog/dialog.h:33:20: curses.h: No such file or directory

etc.

Is this happening to anyone else, and if not, is it because I my target
processor is 386 (not 586 or 686)?

I'd appreciate if someone could do a clean checkout and test this out
rather than simply closing my bug as silly.

Thanks,

Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDf6pfeVDHer2Nu1QRAnFkAJ9DMFlFEuNvdr0HoUPeajOaAzV5VQCdE91s
RRMztZpvFc2CRZc1F6cAGcs=
=6PwE
-----END PGP SIGNATURE-----



More information about the uClibc mailing list