* RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-20 6:32 Richard Davies
0 siblings, 0 replies; 6+ messages in thread
From: Richard Davies @ 2001-07-20 6:32 UTC (permalink / raw)
To: ERICSON, MATHEW (A-Australia, ex1); +Cc: gcc-help
> 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.
>
Yes, I'm using the original release. I rarely breath near the
development branch because things do tend to break unexpectedly. I just
let ltconfig break, then manually add the command line length argument
to the config cache file, so make will resume from where it left off.
> 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
>
I'm afraid I can't really help there, maybe Olivia will have some gem
of wisdom.
I would guess something stupid and completely wrong that yacc hasn't
generated the correct file or something of that ilk, but unless I cvs
checkout out the branch (I won't be doing that) I won't have any real
idea of what is wrong.
--
--
RichyBoy
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-20 6:36 ERICSON, MATHEW (A-Australia, ex1)
0 siblings, 0 replies; 6+ messages in thread
From: ERICSON, MATHEW (A-Australia, ex1) @ 2001-07-20 6:36 UTC (permalink / raw)
To: 'richy.boy@clara.co.uk', ERICSON, MATHEW (A-Australia, ex1)
Cc: gcc-help
Richard,
Solved this one - however libstd++v3 still failed due to the pow() duplicate
declaration. This is a known problem but the patch code I found in the
mailing lists seems to differ from current code in cvs for inclhack.def
Did you apply the patch to your inclhack.def to get this to build?
Thanks
mathew
-----Original Message-----
From: Richard Davies [ mailto:richy.boy@clara.co.uk ]
Sent: Friday, 20 July 2001 11:33 PM
To: ERICSON,MATHEW (A-Australia,ex1)
Cc: gcc-help@gcc.gnu.org
Subject: RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions
> 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.
>
Yes, I'm using the original release. I rarely breath near the
development branch because things do tend to break unexpectedly. I just
let ltconfig break, then manually add the command line length argument
to the config cache file, so make will resume from where it left off.
> 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
>
I'm afraid I can't really help there, maybe Olivia will have some gem
of wisdom.
I would guess something stupid and completely wrong that yacc hasn't
generated the correct file or something of that ilk, but unless I cvs
checkout out the branch (I won't be doing that) I won't have any real
idea of what is wrong.
--
--
RichyBoy
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-20 4:48 ERICSON, MATHEW (A-Australia, ex1)
0 siblings, 0 replies; 6+ messages in thread
From: ERICSON, MATHEW (A-Australia, ex1) @ 2001-07-20 4:48 UTC (permalink / raw)
To: ERICSON, MATHEW (A-Australia, ex1),
'richy.boy@clara.co.uk',
gcc-help
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-20 4:37 ERICSON, MATHEW (A-Australia, ex1)
0 siblings, 0 replies; 6+ messages in thread
From: ERICSON, MATHEW (A-Australia, ex1) @ 2001-07-20 4:37 UTC (permalink / raw)
To: 'richy.boy@clara.co.uk', gcc-help
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-20 1:29 Richard Davies
0 siblings, 0 replies; 6+ messages in thread
From: Richard Davies @ 2001-07-20 1:29 UTC (permalink / raw)
To: gcc-help
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* GCC 3.0 HP-UX 11.00 64bit Build Instructions
@ 2001-07-19 18:16 ERICSON, MATHEW (A-Australia, ex1)
0 siblings, 0 replies; 6+ messages in thread
From: ERICSON, MATHEW (A-Australia, ex1) @ 2001-07-19 18:16 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'
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
1. Ensure correct librarys/headers are installed. My system has
64-bitDevLibs B.11.00 Cross Platform Development Kit
B8110AA 1.2.2.08.00 Java 2 SDK for HP-UX (700/800), PA1.1
+ PA2.0 Add On
B9788AA 1.3.0.01 Java 2 SDK 1.3 for HP-UX (700/800),
PA1.1 + PA2.0 Add On
HPUXEng64RT B.11.00.01 English HP-UX 64-bit Runtime
Environment
Integ-Logon B.11.00 Integrated Logon Bundle
KernDev B.11.00 HPUX Kernel Developers Kit
UXCoreMedia B.11.00.02 HP-UX Media Kit (Reference Only. See
Description)
XSWGR1100 B.11.00.53.2 HP-UX General Release
Patches, June 2001
XSWHWCR1100 B.11.00.53.8 HP-UX Hardware Enablement and
Critical Patches, June 2001
2. Login as root/gcc user.
3. export PATH=/usr/bin (so only /usr/bin/cc is used for build)
4. download and build GNU make 3.79.1
5. export PATH=$PATH:/path/to/gnu/make
6. cd /usr/local/src
7. cp <gcc-3.0.tar.gz> /usr/local/src
8. gzcat gcc-3.0.tar.gz | tar xvf -
9. mkdir objdir
10. cd objdir
11. /usr/local/src/gcc-3.0/configure --prefix=/opt/gcc-3.0 \
--enable-shared \
--without-gnu-as \
--enable-threads=posix \
--enable-languages="c"
12. whence make (ensure this matches GNU make)
13. make bootstrap
14. make install
15. build binutils with newly built gcc 3.0 (c compiler only)
16. export PATH=$PATH:/path/to/binutils
17. cd /usr/local/src/objdir
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++"
19. whence make (ensure this is GNU make)
20. make bootstrap
21. make install
22. Possibly rebuilt GNU make/GNU binutils with new gcc 3.0.
Can anyone sanity check these steps? Tell me if I have missed anything?
Also - does this build 64bit gcc-3.0 or 32bit ? Do you need to install
both 32-bitDevLibs and 64-bitDevLibs?
Mathew Ericson
CC/Unix System Administrator
Agilent @ND R&D
+613 9210-5956
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-07-20 6:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-20 6:32 GCC 3.0 HP-UX 11.00 64bit Build Instructions Richard Davies
-- strict thread matches above, loose matches on Subject: below --
2001-07-20 6:36 ERICSON, MATHEW (A-Australia, ex1)
2001-07-20 4:48 ERICSON, MATHEW (A-Australia, ex1)
2001-07-20 4:37 ERICSON, MATHEW (A-Australia, ex1)
2001-07-20 1:29 Richard Davies
2001-07-19 18:16 ERICSON, MATHEW (A-Australia, ex1)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).