Build errors

Brian Dessent brian@dessent.net
Tue Apr 8 06:07:00 GMT 2008


Yang Zhang wrote:

> In file included from ../.././gcc/unwind-dw2.c:40:
> ../.././gcc/unwind-pe.h:103: error: expected '=', ',', ';', 'asm' or
> '__attrib       ute__' before 'base_of_encoded_value'
> ../.././gcc/unwind-pe.h:133: error: expected declaration specifiers or
> '...' before '_Unwind_Word'
> ../.././gcc/unwind-pe.h: In function 'read_uleb128':
> ../.././gcc/unwind-pe.h:137: error: '_Unwind_Word' undeclared (first use
> in this function)
> ../.././gcc/unwind-pe.h:137: error: (Each undeclared identifier is
> ...
> ./configure --target=x86_64-jos-linux --prefix=/opt/gcc-4.1.2-jos-linux
> --disable-nls --without-headers --with-newlib --disable-threads
> --disable-shared --disable-libmudflap --disable-libssp
> 
> make && make install

Why are you using --without-headers with a linux target?  The docs say:

> --without-headers
> 
> Tells GCC not use any target headers from a libc when building a cross 
> compiler. When crossing to GNU/Linux, you need the headers so GCC can 
> build the exception handling for libgcc.

So that is why your build fails.

The real question is what are you trying to do -- what libc are you
really using?  Is your target actually using newlib and not glibc?  Do
you really mean to build a crosscompiler and not a native?

Brian



More information about the Gcc-help mailing list