Compiling DROPS' dietlibc on FreeBSD

[Martin Pohlack]

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.

But I'm not sure whether dietlibc will build on a bsd, because its author
seems "a little bit" affixed to Linux ;-).

Martin


> Hello,
>
> after changing minimal parts of dietlibc's build procedure, I get as
> far as cd pkg/dietlibc ; gmake actually doing something but it fails
> with the following error:
>
>   ... Compiling lib/__v_printf.o
> LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so
> GENDEP_TARGET=lib/__v_printf.o GENDEP_BINARY=cc1  gcc33 -c
> -nostdinc    -DRAM_BASE=0x0 -DUSE_DIETLIBC=y    -DSYSTEM_x86_686
> -DARCH_x86 -DCPUTYPE_686 -DL4API_ -I../include -I..
> -I../../../idl/OBJ-x86- -I/include -gstabs+     -g -O2
> -fno-strict-aliasing  -march=i686 -Wall -Wstrict-prototypes
> -Wmissing-prototypes
> -Wmissing-declarations
> /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c
> -o
> lib/__v_printf.o
> /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:2:20:
> stdarg.h: No such file or directory In file included
> from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7:
> ../dietstdio.h:12:20:
> stdarg.h: No such file or directory In file included
> from ../dietstdio.h:52,
> from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7:
> ../include/stdio.h:7:20:
> stdarg.h: No such file or directory In file included
> from ../dietstdio.h:52,
> from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7:
>
> The include directories look bogus, but I am quite puzzled where they
> come from. Maybe my directory layout is somehow different from what
> is expected? Any hint is greatly appreciated.
>
> Regards,
> --
> Julian Stecklina
>
> Lisp nearing the age of 50 is the most modern language out
> there. GC, dynamic, reflective, the best OO model extant including
> GFs, procedural macros, and the only thing old-fashioned about it
> is that it is compiled and fast.   -- Kenny Tilton, comp.lang.python
>