Error output:

<<<<
In file included from ../../../gcc-4.3.1/libgcc/../gcc/unwind-dw2.c:41:
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:133: error: expected declaration
specifiers or '...' before '_uleb128_t'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h: In function 'read_uleb128':
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:137: error: '_uleb128_t'
undeclared (first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:137: error: (Each undeclared
identifier is reported only once
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:137: error: for each function it
appears in.)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:137: error: expected ';' before
'result'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:139: error: 'result' undeclared
(first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:143: error: expected ')' before
'byte'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:148: error: 'val' undeclared
(first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h: At top level:
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:155: error: expected declaration
specifiers or '...' before '_sleb128_t'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h: In function 'read_sleb128':
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:159: error: '_uleb128_t'
undeclared (first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:159: error: expected ';' before
'result'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:161: error: 'result' undeclared
(first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:165: error: expected ')' before
'byte'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:172: error: expected ')' before
numeric constant
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:174: error: 'val' undeclared
(first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:174: error: '_sleb128_t'
undeclared (first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:174: error: expected ';' before
'result'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h: In function
'read_encoded_value_with_base':
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:218: error: '_uleb128_t'
undeclared (first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:218: error: expected ';' before
'tmp'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:219: error: 'tmp' undeclared
(first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:219: error: too many arguments to
function 'read_uleb128'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:226: error: '_sleb128_t'
undeclared (first use in this function)
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:226: error: expected ';' before
'tmp'
../../../gcc-4.3.1/libgcc/../gcc/unwind-pe.h:227: error: too many arguments to
function 'read_sleb128'
make[3]: *** [unwind-dw2.o] Error 1
make[3]: Leaving directory
`/c/_Builds/gcc-4.3.1-mingw-build/i686-pc-mingw32/libgcc'
make[2]: *** [all-stage1-target-libgcc] Error 2
make[2]: Leaving directory `/c/_Builds/gcc-4.3.1-mingw-build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/c/_Builds/gcc-4.3.1-mingw-build'
make: *** [all] Error 2
>>>>

This is because type _uleb128_t doesn't properly defined in context of
"/gcc/unwind-dw2.c" in sources of GCC. Type is defined in "unwind-generic.h" in
the same directory, but at first - it doesn't included, at second - it declares
guard define "_UNWIND_H" which already declared in
"/mingw/lib/gcc/mingw32/3.4.5/include/unwind.h" and this file already included,
so try to include "unwind-generic.h" just before "unwind-pe.h" in
"unwind-dw2.c" anyway useless and could invoke different errors.


-- 
           Summary: Type _uleb128_t doesn't defined properly in /gcc/unwind-
                    dw2.c
           Product: gcc
           Version: 4.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: andry at inbox dot ru
  GCC host triplet: i686-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36545

Reply via email to