Re: Files missing and parse errors - toolchain?

["Rowan Potgieter" <baldo dot forum at gmail dot com>]

Ok I think I may have found the problem, but I'm still getting other
errors perhaps somebody could explain this to me.
In the file snapgear/lib/libnet/Makefile I uncommented this line at
the top of the Makefile:
CFLAGS += -I../libc/include
and it seems to have helped it find the includes, however now i get this error:

make[2]: Entering directory
`/home/satvika/stareast/snapgear/snapgear/lib/libnet'
arm-linux-gcc -mbig-endian -O2  -fno-builtin -DEMBED -nostdinc
-I/home/satvika/stareast/snapgear/snapgear/lib/glibc-2.3.3/build/include
-I/home/satvika/stareast/snapgear/snapgear -Dlinux -D__linux__ -Dunix
-I/home/satvika/stareast/snapgear/snapgear/linux-2.4.x/include
-idirafter /opt/crosstool/gcc-3.4.4-glibc-2.3.3/armeb-linux/lib/gcc/armeb-linux/3.4.4//include
-I../libc/include -DL_openraw -o openraw.o -c net.c
In file included from ../libc/include/stdio.h:9,
                from net.c:12:
../libc/include/stdarg.h:3:28: machine/stdarg.h: No such file or directory
In file included from net.c:12:
../libc/include/stdio.h:125: error: parse error before "va_list"
../libc/include/stdio.h:126: error: parse error before "va_list"
../libc/include/stdio.h:127: error: parse error before "va_list"
../libc/include/stdio.h:129: error: parse error before "va_list"
../libc/include/stdio.h:130: error: parse error before "va_list"
../libc/include/stdio.h:131: error: parse error before "va_list"
../libc/include/stdio.h:132: error: parse error before "va_list"
In file included from ../libc/include/sys/param.h:10,
                from ../libc/include/time.h:27,
                from ../libc/include/sys/time.h:58,
                from net.c:18:
../libc/include/limits.h:112:26: no include path in which to search for limits.h
In file included from ../libc/include/dirent.h:36,
                from net.c:19:
../libc/include/limits.h:112:26: no include path in which to search for limits.h
make[2]: *** [libnet.a(openraw.o)] Error 1
make[2]: Leaving directory `/home/satvika/stareast/snapgear/snapgear/lib/libnet'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/satvika/stareast/snapgear/snapgear/lib'
make: *** [subdirs] Error 1

do I need to maybe change other Makefiles or is what I did actually
making things worse?

On 14/08/06, Dimitry Andric <dimitry@andric.com> wrote:
> JulyClyde wrote:
> > glibc  is made after gcc being made.
>
> Yes, but he's not building glibc, he's building something else, some
> snapgear library:
>
> make[2]: Entering directory `/home/satvika/stareast/snapgear/snapgear/lib/libnet'
> arm-linux-gcc -mbig-endian -O2  -fno-builtin -DEMBED -nostdinc -I/home/satvika/stareast/snapgear/snapgear/lib/glibc/build/include -I/home/satvika/stareast/snapgear/snapgear -Dlinux -D__linux__ -Dunix -I/home/satvika/stareast/snapgear/snapgear/linux-2.4.x/include -idirafter /opt/crosstool/gcc-3.4.4-glibc-2.3.3/armeb-linux/lib/gcc/armeb-linux/3.4.4//include -DL_openraw -o openraw.o -c net.c
> net.c:12:19: stdio.h: No such file or directory
> net.c:13:20: unistd.h: No such file or directory
> net.c:14:20: stdlib.h: No such file or directory
> ...
>
> As you can see, the snapgear Makefile defines -nostdinc, and that causes
> the proper glibc headers to be missed.  I guess snapgear needs to define
> its own headers, but fails to find them, or something else is wrong.
>
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq


--
--------------------------------------------------------------------------------------------------------------------------------------------
When you say 'I wrote a program that crashed Windows', people just
stare at you blankly and say 'Hey, I got those with the system, *for
free*'. (L. Torvalds)
--------------------------------------------------------------------------------------------------------------------------------------------

--
For unsubscribe information see http://sourceware.org/lists.html#faq