GCC 3.0 HP-UX 11.00 64bit Build Instructions

[ERICSON, MATHEW (A-Australia, ex1)]

Richard,

Scratch that - error was caused by using HPUX make(1) instead of GNU
make(1). Reset $PATH correctly and build continues...stay tuned...

Thanks
mathew

-----Original Message-----
From: ERICSON,MATHEW (A-Australia,ex1) [ mailto:mathew_ericson@agilent.com ] 
Sent: Friday, 20 July 2001 9:38 PM
To: 'richy.boy@clara.co.uk'; gcc-help@gcc.gnu.org
Subject: RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions

Richard,

Thankyou for shedding somelight on this matter I am forging ahead - spirits
renewed knowing that atleast someone else has this working.

Another question though - which version of gcc-3.0 are you building? The
original release has the ltconfig error determining maximum length of
command line arguments. 

I am currently synced to gcc-3.0-branch but this does not build failing
during stage1 with:

./genflags /usr/local/src/gcc-snapshot/gcc_snapshot/gcc/gcc/config/pa/pa
.md > tmp-flags.h
/bin/sh /usr/local/src/gcc-snapshot/gcc_snapshot/gcc/gcc/move-if-change
tmp-flags.h insn-flags.h
echo timestamp > s-flags
(cd /usr/local/src/gcc-snapshot/gcc_snapshot/gcc/gcc && false  -o c-p$$.
c c-parse.y && \
mv -f c-p$$.c c-parse.c)
*** Error exit code 1
Stop.
*** Error exit code 1
Stop.
*** Error exit code 1
Stop.

Thanks again
mathew

-----Original Message-----
From: Richard Davies [ mailto:richy.boy@clara.co.uk ] 
Sent: Friday, 20 July 2001 6:29 PM
To: gcc-help@gcc.gnu.org
Subject: Re: GCC 3.0 HP-UX 11.00 64bit Build Instructions

> Dear gcc-help,
> 
> I have been trying to build gcc-3.0 for some time now and want to 
document a
> firm set of instructions for building. Could the HP-UX maintainers 
please
> help me in setting this list of instructions
> 

You don't need to do a lot of those steps. 

> 1. Ensure correct librarys/headers are installed. My system has

You might want to install other such patches, also makesure you install 
the patches in 64 bit mode (it's not default).

B6733AA B.11.00.10 DCE/9000 Kernel Threads Support
PHKL_14750 1.0 Fix pthread_cond_timedwait(3T) error return 
PHKL_17935 1.0 libpthreads cumulative patch


> 11. /usr/local/src/gcc-3.0/configure --prefix=/opt/gcc-3.0 \
--enable-shared \
--without-gnu-as \
--enable-threads=posix \
--enable-languages="c"

personally I would build binutils first with the native compiler, then 
build gcc. Then perhaps rebuild the binutils with gcc but it hardly 
matters. Just in cae you do have gnu ld laying around I would do --
without-gnu-ld as it does  break unexpectedly on 64 bit shared librarys.
(building ACE for example)

> 18. /usr/local/src/gcc-3.0/configure --prefix=/opt/gcc-3.0 \
--enable-shared \
> --with-gnu-as \
> --enable-threads=posix \
> --enable-languages="c,c++"

You wouldn't really need to build the compiler again, there is no need 
for it. The stage 1 compiler builds the stage 2 compiler so there is 
nothing to be gained here at all. If you are worried about as build 
binutils before hand.. the as exec may be a little different but it *
will* output exactly the same code as before.

> 22. Possibly rebuilt GNU make/GNU binutils with new gcc 3.0.

As a matter of note this is my gcc -v output:
Configured with: ../configure --prefix=/home/users/daviesr/local --
enable-shared=libstdc++ --with-gnu-as --enable-threads=posix --enable-
languages=c++ --enable-version-specific-runtime-libs --with-as=/home/
users/daviesr/local/bin/as : (reconfigured) ../configure --prefix=/home/
users/daviesr/local --enable-shared=libstdc++ --with-gnu-as --enable-
threads=posix --enable-languages=c++,objc --enable-version-specific-
runtime-libs --with-as=/home/users/daviesr/local/bin/as
Thread model: posix
gcc version 3.0

One point though, building the Standard C++ Library is likely to fail 
on the first pass, ltconfig is broken for some reason I can't quite 
work out so you might have to manually add something to the appropriate 
config.cache file to force it to work.

> Also - does this build 64bit gcc-3.0 or 32bit ? Do you need to 
install

It's 64 bit, 2.95.2 didn't support HP-UX 11 afair, but gcc-3.0 does 
because it's 64 bits. 

Still my word is not definitive, just being a good friday samariten.

-- 
-- 

RichyBoy