Zitat von Thomas Mittelstaedt <T.Mittelstaedt@xxxxxxxxxx>:
With a lot of ugly fixing in generated Makefile's, I got past stage 3,
but now libstdc++ does not build.
The generated config.h in hppa64-hp-hpux11.11/libstdc++-v3 seems to be
wrong, as there is an fabsf and altera
on my system, at least in the headers.
That's how we succed after some trouble when compiling GCC 4.2.2 on
HP-UX 11.11 (PA-RISC) :
export CONFIG_SHELL=/usr/bin/bash
(Installed from OSS Archiv)
export LANG=C
(wird für gcc 4.x wegen awk/sed auf HPUX und AIX benötigt!!)
export CC=<verwendeter Compiler>
We used some gcc 3.4.x in 32/64Bit build
Config/Build für PA-32Bit 4.2.2: ../configure --prefix=/opt/gcc-4.2.2
--mandir=/usr/local/man --with-gnu-as --with-as=/usr/local/bin/gnu-as
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --disable-nls
--enable-threads=posix --enable-languages=c,c++
Config/Build für PA-64Bit 4.2.2: ../configure
--prefix=/opt/gcc64-4.2.2 --mandir=/usr/local/man
--with-ar=/usr/bin/ar --with-gnu-as --with-as=/usr/local/bin/gnu64-as
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --disable-nls
--enable-threads=posix --enable-languages=c,c++
Important is to *not* use the OS "as" but use some GNU-as with the
matching 32/64Bit build. For the "ld" you should use the OS "ld", but
your system should be on a recent patchlevel. It is useful to have GNU
"awk" and "sed" instead of the OS ones.
For all of the used tools you should always double-check if the
intentioned one is used by configure.
Regards & good luck
Andreas
