On Tue, 13 Sep 2005 11:27:21 +0200 (DFT) "Martin Pohlack" mp26@os.inf.tu-dresden.de wrote:
Hi,
I currently don't have access to the source code, but I think you should look up how the gcc include path is generated. The '-I/include' and the missing 'stdarg.h' seem to point to this.
I changed GCCDIR_x86 to /usr, so /usr/include gets passed and most of dietlibc seems to compile. But I am missing l4/* include files. What is the required order of building? How do I install header files where the build scripts find them?
... Compiling _exit.o LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so GENDEP_TARGET=_exit.o GENDEP_BINARY=cc1 gcc33 -c -DRAM_BASE=0x0 -DUSE_DIETLIBC=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../../idl/OBJ-x86-l4v2 -I../../../../../../include/x86/l4v2 -I/home/blitz/drops/include/x86/l4v2 -I../../../../../../include/l4v2 -I/home/blitz/drops/include/l4v2 -I../../../../../../include/x86 -I/home/blitz/drops/include/x86 -I../../../../../../include -I/home/blitz/drops/include -nostdinc -DUSE_DIETLIBC=y -I../../../../../../include/dietlibc -I/home/blitz/drops/include/dietlibc -I/usr/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/blitz/src/l4/pkg/dietlibc/lib/backends/l4_start_stop/_exit.c -o _exit.o /home/blitz/src/l4/pkg/dietlibc/lib/backends/l4_start_stop/_exit.c:13:26: l4/crtx/crt0.h: No such file or directory /home/blitz/src/l4/pkg/dietlibc/lib/backends/l4_start_stop/_exit.c:14:26: l4/util/util.h: No such file or directory
But I'm not sure whether dietlibc will build on a bsd, because its author seems "a little bit" affixed to Linux ;-).
I have high hopes. It cannot be _that_ difficult. But if someone could explain to me where the advantage of find -printf "%P " over find -print is (which is POSIX) I would be partially enlightened. ;)
Regards,