From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Architecture string change
Date: 10 Jul 2000 17:45:14 -0400 [thread overview]
Message-ID: <87og45bqxh.fsf@linuxcare.com> (raw)
Hi,
In keeping with the way things are done on other Linux platforms, I
would like us to start using the following architecture strings for
configuring our compilers:
32-bit userland and kernel, PA1.1: hppa-linux
64-bit kernel, PA2.0: hppa64-linux
I guess this means that I volunteer to update the recipes on the
website :-)
config.guess will return a more detailed string, such as
'hppa2.0-unknown-linux-gnu', but these should be the canonical,
lowest-common-denominator strings. In particular, we should revise
the recipes and such to use them and configure dpkg-architecture to
set DEB_GNU_HOST_ARCH to 'hppa-linux'.
I have not been able to get a solid answer out of anyone regarding
whether it is possible or desireable to use 'parisc-' instead of
'hppa-', so I will leave it as 'hppa' for the time being. It is easy
enough to make 'parisc' an alias for 'hppa' if we want to.
Some pros and cons of using 'parisc' vs. 'hppa':
* Pro: hppa*-linux targets produce very different 32-bit object code,
as well as different 64-bit assembly code, so it may be beneficial
to distinguish them from other PA-RISC targets.
* Pro: I'm told that people at HP want to use 'parisc'. Could those
people please stand up :-)
* Con: config.guess [1] will presumably return hppa*-*-linux-gnu.
* Con: Every other operating system on PA-RISC uses hppa*-*-*.
(I know there are some more but I can't think of them right now)
Please remember that, now that we are entering userspace, any
decisions of this sort that we make are going to stick with us
forever. [2]
[1] Which I can't actually run since our page fault handler is broken:
> /bin/sh config.guess
do_page_fault() pid=8 command='sh'
Bad Address (null pointer deref?): Code=15 regs=c7e5c248 (Addr=00000001)
PSW : 0004f80b GR 1 : 00090350 GR 2 : 00007f4f GR 3 : 00092e28
GR 4 : 00000000 GR 5 : 00092b50 GR 6 : 00000019 GR 7 : 0000000e
GR 8 : 00000001 GR 9 : 00092e28 GR10 : ffffffff GR11 : 200206e2
GR12 : 0000000a GR13 : 00094b50 GR14 : 0007f621 GR15 : 00000000
GR16 : 00094f0c GR17 : 00000000 GR18 : 0000000e GR19 : 00000001
GR20 : 40100868 GR21 : 00000001 GR22 : 00000000 GR23 : 40100030
GR24 : 40100848 GR25 : 00000020 GR26 : 40100010 GR27 : 0008f350
GR28 : 40100850 GR29 : 00000001 GR30 : 20020880 GR31 : 000171d7
SR0 : 00002001 SR1 : 00002001 SR2 : 00000100 SR3 : 00002001
SR4 : 00002001 SR5 : 00002001 SR6 : 00002001 SR7 : 00002001
IASQ : 00002001 00002001 IAOQ : 00007f53 00007f57
IIR : 0e7c1280 ISR : 00002001 IOR : 00000001
[2] A good example of this is how the soname for glibc is
'libc.so.6.1' on Linux/alpha instead of 'libc.so.6' due to a screwup
in an early Red Hat distribution...
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next reply other threads:[~2000-07-10 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 21:45 David Huggins-Daines [this message]
2000-07-10 22:59 ` [parisc-linux] Architecture string change Grant Grundler
2000-07-10 23:04 ` John David Anglin
2000-07-11 1:55 ` Bdale Garbee
2000-07-11 14:28 ` David Huggins-Daines
2000-07-11 18:15 ` Andrew Shugg
2000-07-11 18:36 ` John David Anglin
2000-07-11 10:18 ` Corne Beerse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87og45bqxh.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox