Problem building gcc 3.2 on powerpc-ibm-aix5.1.0.0

Jose jperezme@mi.madritel.es
Tue Jan 21 23:22:00 GMT 2003


Looking at www.bullfreeware.com . They are there in installp format.


----------------------------------------------------------------
Tu portal de Aix en Español
http://aixpanish.com
------------------------------------------------------------

----- Original Message -----
From: <Brendan_E_Martin@vfc.com>
To: <gcc-help@gcc.gnu.org>
Sent: Tuesday, January 21, 2003 9:51 PM
Subject: Problem building gcc 3.2 on powerpc-ibm-aix5.1.0.0


> Getting the following output at the end of build attempts:
>
> make[3]: Leaving directory `/usr/local/build/gcc/intl'
> cc -c -DIN_GCC    -g    -DHAVE_CONFIG_H    -I. -I.
> -I/usr/local/src/gcc-3.2/gcc -I/usr/local/src/gcc-3.2/gcc/.
> -I/usr/local/src/gcc-3.2/gcc/config -I/usr/local/src/gcc-3.2/gcc/../includ
e
> /usr/local/src/gcc-3.2/gcc/tradcif.c -o tradcif.o
> "tradcif.y", line 222.17: 1506-196 (W) Initialization between types
> "unsigned char*" and "const unsigned char*" is not allowed.
> "tradcif.y", line 319.12: 1506-068 (W) Operation between types "unsigned
> char*" and "const unsigned char*" is not allowed.
> "tradcif.y", line 438.1: 1506-343 (S) Redeclaration of parse_escape
differs
> from previous declaration on line 35 of "tradcif.y".
> "tradcif.y", line 438.1: 1506-381 (I) The type "const unsigned char**" of
> parameter 1 in the prototype declaration is not compatible with the
> corresponding parameter type "unsigned char**" in the nonprototype
> declaration.
> make[2]: *** [tradcif.o] Error 1
> make[2]: Leaving directory `/usr/local/build/gcc'
> make[1]: *** [stage1_build] Error 2
> make[1]: Leaving directory `/usr/local/build/gcc'
> make: *** [bootstrap] Error 2
>
> I saw a similar question involving AIX 4.3.3 for which the recommendation
> was to touch all the .y files and make sure that bison is available.  I
> attempted to build bison, but got an error about M4 1.4 being required.  I
> could find no references to M4 at gnu.org.
>
> Any recommendations will be appreciated.
>
> Brendan Martin
>
>
>




More information about the Gcc-help mailing list