Huub wrote:
> Hi,
>
> After installing GNU tar and make, and following the GNU building
> guidelines (e.g. using bash), building gcc-4.2.2 ends in this error:
>
> /software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/xgcc
> -B/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/
> -B/usr/local/powerpc-ibm-aix5.3.0.0/bin/ -c -g -O2 -DIN_GCC -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
> -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
> -Wold-style-definition -Wmissing-format-attribute -Wno-error
> -DHAVE_CONFIG_H -I. -Ijava -I../.././gcc -I../.././gcc/java
> -I../.././gcc/../include -I../.././gcc/../libcpp/include
> -I../.././gcc/../libdecnumber -I../libdecnumber java/parse-scan.c -o
> java/parse-scan.o
> xgcc: java/parse-scan.c: A file or directory in the path name does not
> exist.
> xgcc: no input files
> make[3]: *** [java/parse-scan.o] Error 1
> make[3]: Leaving directory
> `/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/software/gcc-4.2.2'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/software/gcc-4.2.2'
> make: *** [all] Error 2
>
> Can someone please help on this?
>
> Thank you.

Which make is it really calling? Use gmake to be sure? See also other
posts today. tar and make are by no means the full set of requirements
to build ....

> Which make is it really calling? Use gmake to be sure? See also other
> posts today. tar and make are by no means the full set of requirements
> to build ....

I started the build with /usr/local/bin/make, so I assume it has been
calling this all the time during the make. And what are the other parts
of that full set of requirements?

Huub wrote:
>
>> Which make is it really calling? Use gmake to be sure? See also other
>> posts today. tar and make are by no means the full set of requirements
>> to build ....
>
> I started the build with /usr/local/bin/make, so I assume it has been
> calling this all the time during the make. And what are the other parts
> of that full set of requirements?

From http://gcc.gnu.org/install/prerequisites.html


Tools/packages necessary for building GCC

ISO C90 compiler
Necessary to bootstrap GCC, although versions of GCC prior to 3.4
also allow bootstrapping with a traditional (K&R) C compiler.

To build all languages in a cross-compiler or other configuration
where 3-stage bootstrap is not performed, you need to start with an
existing GCC binary (version 2.95 or later) because source code for
language frontends other than C might use GCC extensions.
GNAT
In order to build the Ada compiler (GNAT) you must already have GNAT
installed because portions of the Ada frontend are written in Ada (with
GNAT extensions.) Refer to the Ada installation instructions for more
specific information.
A “working” POSIX compatible shell, or GNU bash
Necessary when running configure because some /bin/sh shells have
bugs and may crash when configuring the target libraries. In other
cases, /bin/sh or ksh have disastrous corner-case performance problems.
This can cause target configure runs to literally take days to complete
in some cases.

So on some platforms /bin/ksh is sufficient, on others it isn't. See
the host/target specific instructions for your platform, or use bash to
be sure. Then set CONFIG_SHELL in your environment to your “good” shell
prior to running configure/make.

zsh is not a fully compliant POSIX shell and will not work when
configuring GCC.
GNU binutils
Necessary in some circumstances, optional in others. See the
host/target specific instructions for your platform for the exact
requirements.
gzip version 1.2.4 (or later) or
bzip2 version 1.0.2 (or later)
Necessary to uncompress GCC tar files when source code is obtained
via FTP mirror sites.
GNU make version 3.79.1 (or later)
You must have GNU make installed to build GCC.
GNU tar version 1.14 (or later)
Necessary (only on some platforms) to untar the source code. Many
systems' tar programs will also work, only try GNU tar if you have problems.
GNU Multiple Precision Library (GMP) version 4.1 (or later)
Necessary to build GCC. If you do not have it installed in your
library search path, you will have to configure with the --with-gmp
configure option. See also --with-gmp-lib and --with-gmp-include.
MPFR Library version 2.3.0 (or later)
Necessary to build GCC. It can be downloaded from
http://www.mpfr.org/. The version of MPFR that is bundled with GMP 4.1.x
contains numerous bugs. Although GCC may appear to function with the
buggy versions of MPFR, there are a few bugs that will not be fixed when
using this version. It is strongly recommended to upgrade to the
recommended version of MPFR.

The --with-mpfr configure option should be used if your MPFR Library
is not installed in your default library search path. See also
--with-mpfr-lib and --with-mpfr-include.
jar, or InfoZIP (zip and unzip)
Necessary to build libgcj, the GCJ runtime.

All requirements have been met except:

> GNU Multiple Precision Library (GMP) version 4.1 (or later)
> Necessary to build GCC. If you do not have it installed in your
> library search path, you will have to configure with the --with-gmp
> configure option. See also --with-gmp-lib and --with-gmp-include.

Ok, got this installed and checked.

> MPFR Library version 2.3.0 (or later)
> Necessary to build GCC. It can be downloaded from
> http://www.mpfr.org/. The version of MPFR that is bundled with GMP 4.1.x
> contains numerous bugs. Although GCC may appear to function with the
> buggy versions of MPFR, there are a few bugs that will not be fixed when
> using this version. It is strongly recommended to upgrade to the
> recommended version of MPFR.
>

This goes wrong on both 32 bits and 64 bits with ./configure:

> checking for __gmpz_init in -lgmp... no
> configure: error: libgmp not found

Any recommendation on this one?

Huub wrote:
> All requirements have been met except:
>
>> GNU Multiple Precision Library (GMP) version 4.1 (or later)
>> Necessary to build GCC. If you do not have it installed in your
>> library search path, you will have to configure with the --with-gmp
>> configure option. See also --with-gmp-lib and --with-gmp-include.
>
> Ok, got this installed and checked.
>
>> MPFR Library version 2.3.0 (or later)
>> Necessary to build GCC. It can be downloaded from
>> http://www.mpfr.org/. The version of MPFR that is bundled with GMP 4.1.x
>> contains numerous bugs. Although GCC may appear to function with the
>> buggy versions of MPFR, there are a few bugs that will not be fixed when
>> using this version. It is strongly recommended to upgrade to the
>> recommended version of MPFR.
>>
>
> This goes wrong on both 32 bits and 64 bits with ./configure:

Did you apply the cumulative patch mentioned here?

http://www.mpfr.org/mpfr-current/#doc

from my config.status :

with options \"'--enable-shared=no' '--with-gmp=/usr/local'
'CFLAGS=-mcpu=common'\"
>
>> checking for __gmpz_init in -lgmp... no
>> configure: error: libgmp not found
>
> Any recommendation on this one?

I went so far at one point to link the static libraies for libgmp and
libmpfr into /usr/lib

Nasty cheat. YMMV, Don't try this at home, etc I think I may have had

ABI=32

at some point too.

HTH

>
> Did you apply the cumulative patch mentioned here?
>
> http://www.mpfr.org/mpfr-current/#doc
>

No, I haven't yet. But I did set configure with

> ./configure --with-gmp-lib=/usr/local/lib

which didn't succeed:

> configure: error: libgmp not found

Also I applied

> export OBJECT_MODE=64

as mentioned under Notes on AIX/PowerPC.
But that got me nowhere as configure ended with a message that the
compiler wasn't able to create executables. U reset OBJECT_MODE as " ",
after which the configure initially ended in the same error as well, but
now it ends with the "libgmp not found" error.

I'm trying this at my 64-bits p44-170 at home. I'll try the patch.

>
> Did you apply the cumulative patch mentioned here?
>
> http://www.mpfr.org/mpfr-current/#doc
>

How exactly did you apply the patch? The -Z or -z option isn't
recognized in AIX.

Huub wrote:
>>
>> Did you apply the cumulative patch mentioned here?
>>
>> http://www.mpfr.org/mpfr-current/#doc
>>
>
> How exactly did you apply the patch? The -Z or -z option isn't
> recognized in AIX.

Use gnu tar. From the toolbox or wherever. As long as gzip and bzip2
are in your path, the -z and -j options will work with it. Definately
not part of the standard tar

> Use gnu tar. From the toolbox or wherever. As long as gzip and bzip2
> are in your path, the -z and -j options will work with it. Definately
> not part of the standard tar

I think here's a misunderstanding. I'm using gnu tar for untarring all
stuff. gzip en bzip2 are in my path. The -z amd -Z option I'm talking
about are from the patch command. Because the patching doesn't work
somehow: "patch -Z -N < patch" errors on -Z.

Huub wrote:
>> Use gnu tar. From the toolbox or wherever. As long as gzip and bzip2
>> are in your path, the -z and -j options will work with it. Definately
>> not part of the standard tar
>
> I think here's a misunderstanding. I'm using gnu tar for untarring all
> stuff. gzip en bzip2 are in my path. The -z amd -Z option I'm talking
> about are from the patch command. Because the patching doesn't work
> somehow: "patch -Z -N < patch" errors on -Z.

Ah, sorry. Same logic, different -z. 8-( /usr/bin/patch that comes
with AIX doesn't have the same options as /opt/freeware/bin/patch from
the IBM toolbox - or wherever you choose to get GNU patch from.

>
> Ah, sorry. Same logic, different -z. 8-( /usr/bin/patch that comes
> with AIX doesn't have the same options as /opt/freeware/bin/patch from
> the IBM toolbox - or wherever you choose to get GNU patch from.

Got it...patched well now. Thank you. Will give another try at ./configure.

> Ah, sorry. Same logic, different -z. 8-( /usr/bin/patch that comes
> with AIX doesn't have the same options as /opt/freeware/bin/patch from
> the IBM toolbox - or wherever you choose to get GNU patch from.

OK, mpfr is installed and checked now on the 32 bits machine. Still not
getting through it though on the 64 bits machine. With the same patches
and configure options, it still can't find the gmplib which there...

> OK, mpfr is installed and checked now on the 32 bits machine. Still not
> getting through it though on the 64 bits machine. With the same patches
> and configure options, it still can't find the gmplib which there...

And I'm back where I started. After installing mpfr on the 32 bits
machine, I went back to building gcc-4.2.2. This ends again with:

/software/gcc-4.2.2/missing bison -t -o java/parse-scan.c
.../.././gcc/java/parse-scan.y
WARNING: `bison' missing on your system. You should only need it if
you modified a `.y' file. You may need the `Bison' package
in order for those modifications to take effect. You can get
`Bison' from any GNU archive site.
/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/xgcc
-B/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/
-B/usr/local/powerpc-ibm-aix5.3.0.0/bin/ -c -g -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-Wold-style-definition -Wmissing-format-attribute -Wno-error
-DHAVE_CONFIG_H -I. -Ijava -I../.././gcc -I../.././gcc/java
-I../.././gcc/../include -I../.././gcc/../libcpp/include
-I../.././gcc/../libdecnumber -I../libdecnumber java/parse-scan.c -o
java/parse-scan.o
xgcc: java/parse-scan.c: A file or directory in the path name does not
exist.
xgcc: no input files
make[3]: *** [java/parse-scan.o] Error 1
make[3]: Leaving directory
`/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/software/gcc-4.2.2'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/software/gcc-4.2.2'
make: *** [all] Error 2
$

Any more suggestions?

Huub wrote:
>> OK, mpfr is installed and checked now on the 32 bits machine. Still
>> not getting through it though on the 64 bits machine. With the same
>> patches and configure options, it still can't find the gmplib which
>> there...
>
> And I'm back where I started. After installing mpfr on the 32 bits
> machine, I went back to building gcc-4.2.2. This ends again with:
>
> /software/gcc-4.2.2/missing bison -t -o java/parse-scan.c
> ../.././gcc/java/parse-scan.y
> WARNING: `bison' missing on your system. You should only need it if
> you modified a `.y' file. You may need the `Bison' package
> in order for those modifications to take effect. You can get
> `Bison' from any GNU archive site.
> /software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/xgcc
> -B/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/prev-gcc/
> -B/usr/local/powerpc-ibm-aix5.3.0.0/bin/ -c -g -O2 -DIN_GCC -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
> -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
> -Wold-style-definition -Wmissing-format-attribute -Wno-error
> -DHAVE_CONFIG_H -I. -Ijava -I../.././gcc -I../.././gcc/java
> -I../.././gcc/../include -I../.././gcc/../libcpp/include
> -I../.././gcc/../libdecnumber -I../libdecnumber java/parse-scan.c -o
> java/parse-scan.o
> xgcc: java/parse-scan.c: A file or directory in the path name does not
> exist.
> xgcc: no input files
> make[3]: *** [java/parse-scan.o] Error 1
> make[3]: Leaving directory
> `/software/gcc-4.2.2/host-powerpc-ibm-aix5.3.0.0/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/software/gcc-4.2.2'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/software/gcc-4.2.2'
> make: *** [all] Error 2
> $
>
> Any more suggestions?

OK, when installed from the toolbox, bison is in /opt/freeware/bin/bison
and linked into /usr/lib. Yours is ....?

>
> OK, when installed from the toolbox, bison is in /opt/freeware/bin/bison
> and linked into /usr/lib. Yours is ....?

From the toolbox and installed in /opt/freeware/bin and /usr/bin/bison
linked to it.

Huub wrote:
>>
>> OK, when installed from the toolbox, bison is in /opt/freeware/bin/bison
>> and linked into /usr/lib. Yours is ....?
>
> From the toolbox and installed in /opt/freeware/bin and /usr/bin/bison
> linked to it.

Ooops, I meant /usr/bin as you said.

Well, I cannot duplicate the bison error (??) but I can duplicate the
java/parse-scan error on both 5.2 and 5.3. 'Fraid at the moment I am as
stumped as anyone.

But I will keep scratching the appropriate parts of my anatomy. 8-)

And you could, it seems, build the c, c++ and fortran in the meantime.

Sorry.

Timothy J. Bogart wrote:
> Huub wrote:
>>> OK, when installed from the toolbox, bison is in /opt/freeware/bin/bison
>>> and linked into /usr/lib. Yours is ....?
>> From the toolbox and installed in /opt/freeware/bin and /usr/bin/bison
>> linked to it.
>
> Ooops, I meant /usr/bin as you said.
>
> Well, I cannot duplicate the bison error (??) but I can duplicate the
> java/parse-scan error on both 5.2 and 5.3. 'Fraid at the moment I am as
> stumped as anyone.
>
> But I will keep scratching the appropriate parts of my anatomy. 8-)
>
> And you could, it seems, build the c, c++ and fortran in the meantime.
>
> Sorry.

Finally stumbled across something. bison-1.875-3 turns out to be quite
broken. Dropping back to bison-1.34-2 seems to allow me to build c,
c++, fortan, java and objc.

HTH