From: Jeffrey A Law <law@cygnus.com>
To: rodneybrown@pmsc.com
Cc: egcs@cygnus.com
Subject: Re: Patches to 19981213 config.guess etc for HPPA2.0 support
Date: Thu, 17 Dec 1998 21:18:00 -0000 [thread overview]
Message-ID: <8384.913958227@upchuck> (raw)
In-Reply-To: <9812179139.AA913941102@cc.pmsc.com>
In message < 9812179139.AA913941102@cc.pmsc.com >you write:
> Heres the evidence for the general 9000/[678][0-9][0-9] pattern
> for HP numeric model numbers.
I spent some time thinking about the model # stuff, and after looking at the
HP recommended code to get the system's architecture I decided to rely on
the C code to get the architecture. The fallback code based on model #s is
mostly obsolete now -- I don't really care if the fallback code mis-identifies
a particular model -- so long as it does so in a safe manner.
> Also shouldn't {,{gcc,texinfo}/}config.sub be the one hard-linked file?
> The differences seem to be in stages of evolution, rather than active.
gcc/config.sub has been targeted for termination. texinfo/config.sub will
probably hang around much longer since we do not control the texinfo package.
jeff
prev parent reply other threads:[~1998-12-17 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-17 16:30 rodneybrown
1998-12-17 21:18 ` Jeffrey A Law [this message]
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=8384.913958227@upchuck \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=rodneybrown@pmsc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).