This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: hpux: howto force use of pa2.0?


Jeffrey A Law wrote:

>   In message <39E2FA79.7076178B@lufmech.rwth-aachen.de>you write:
>   > Hi!
>   >
>   > Even though I configured for hppa2.0w-hp-hpux11.00,
>   > g++ calls collect2 with paths to /lib/pa1.1 instead of /lib/pa20_64
>   >
>   > # g++ -v [...]
>   >
>   > /work/markus/opt/egcs-test/lib/gcc-lib/hppa2.0w-hp-hpux11.00/2.97/collect2
>   >
>   > -L/lib/pa1.1 -L/usr/lib/pa1.1 [...]
>   >
>   >
>   > Is this correct? How can I force the use of pa2.0 64 bit whenever it is
>   > possible?
> If you want to use PA64, then you need to configure with hppa64-hp-hpux11.00

Then the "w" in hppa2.0w-hp-hpux11.00 is in contradiction to hp's naming
convention and misleading the user: the options of hp's cc extracted from cc
man page read
-------------------------------------------------------------
                             Examples
                                         +DA1.1
                                         +DA867
                                         +DA2.0
                                         +DA2.0W
                                         +DAportable

                             The first two examples generate code for the
                             PA-RISC 1.1 architecture. The third example
                             generates 32-bit code for the PA-RISC 2.0
                             architecture. The fourth example generates 64-
                             bit code for the PA-RISC 2.0 architecture.  The
                             fifth example generates code compatible across
                             PA-RISC 1.1 and 2.0 workstations and servers.
---------------------------------------------------------

Maybe hppa2.0w-hp-hpux11.00 should be renamed hppa2.0-hp-hpux11.00
to prevent hp users from expecting things they do not get.

But even then if I configure for hppa2.0-hp-hpux11.00
I would not expect PA-RISC1.1 binaries and a compiler
that generates PA-RISC1.1 binaries per default.

So maybe hosttype hppa2.0-hp-hpux11.00 should be deleted
from the list of valid host types ...

The whole gcc host naming convention IMHO makes no sense
for the hppa part.


Btw.: 64 bit seems to be far from being an option on my system.
See http://sources.redhat.com/ml/binutils/2000-10/msg00107.html
for further problems I have trying to obtain 64-bit binutils on hpux-11.0
Has anyone tried this before?

Markus


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]