-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John David Anglin schrieb: >> Perhaps I have to be more precise. Bootstrapping ada failed! > > That's not enough! In order for someone else to duplicate the failure > and investigate the problem, you need to provide the log of what happened, > your configure command, etc. For example, I would have never guessed that > you were using "-mpa-risc-2-0". See http://gcc.gnu.org/bugs.html. > > Dave
Ok, I did a bootstrap and testsuite run without passing -mpa-risc-2-0 to the boostrap compiler. Testresults including configure options and environment at http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01297.html the only acats test that failed: c52103x That's really good. I will try current 4.0 end of the week. A few words to the -mpa-risc-2-0 switch: As the documentation says, there are two different target for hppa*-hp-hpux11*: The `hppa[1-2]*-hp-hpux11*' target generates code for the 32-bit PA-RISC runtime architecture and uses the HP linker. The `hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0 architecture. For the target `hppa[1-2]*-hp-hpux11*' gcc --target-help says: - -mpa-risc-2-0 Generate PA2.0 code (requires binutils 2.10 or later) - -mpa-risc-1-1 Generate PA1.1 code - -mpa-risc-1-0 Generate PA1.0 code which produces executables as follows for example: file gcc gcc: PA-RISC1.1 shared executable dynamically linked -not stripped or file gcc gcc: PA-RISC2.0 shared executable dynamically linked -not stripped these are 32bit. For the target `hppa64-hp-hpux11*' it's completly different: file gcc gcc: ELF-64 executable object file - PA-RISC 2.0 (LP64) this is 64bit. So what I see, the `hppa64-hp-hpux11*' target implies PA-RISC 2.0 architecture. But I think it's not true the other way. The `hppa[1-2]*-hp-hpux11*' target does not imply 64bit. curios enough gcc build for target `hppa64-hp-hpux11*' has the same output for - --target-help - -mpa-risc-2-0 Generate PA2.0 code (requires binutils 2.10 or later) - -mpa-risc-1-1 Generate PA1.1 code - -mpa-risc-1-0 Generate PA1.0 code So, what I did in the past: I set CC="gcc -mpa-risc-2-0". This forces gcc and all drivers to be built for PA-RISC2.0. Runtime libraries are built for PA-RISC1.1, because gcc defaults to build PA-RISC1.1 code for target hppa2.0w-hp-hpux11.00, that's also curios. This works for all languages except ada, as you can see at http://gcc.gnu.org/ml/gcc-testresults/2005-11/msg00897.html Perhaps somebody may enlight me, if I'm wrong. Rainer - -- Rainer Emrich TECOSIM GmbH Im Eichsfeld 3 65428 Rüsselsheim Phone: +49(0)6142/8272 12 Mobile: +49(0)163/56 949 20 Fax.: +49(0)6142/8272 49 Web: www.tecosim.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD16Zs3s6elE6CYeURAoYoAKDemWfq7KMjc2JaJk2b3lPC4rAYUwCgk7VM 6x7who5BqwJaoTxfDnx3d40= =8Zoh -----END PGP SIGNATURE-----
