From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Ben Elliston <bje@wasabisystems.com>
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com,
gdb@sources.redhat.com, rms@gnu.org, eggert@cs.ucla.edu
Subject: Re: flag day for Solaris portions of config.{guess,sub}
Date: Thu, 20 Nov 2003 14:12:00 -0000 [thread overview]
Message-ID: <yddu14z3z8z.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Ben Elliston's message of "20 Nov 2003 20:31:40 +1100"
Ben Elliston <bje@wasabisystems.com> writes:
> Paul Eggert has been asking over the course of the last year when
> config.{guess,sub} will start to correctly identify Solaris version
> numbers. The problem is that config.guess misidentifies Solaris 7, 8,
> and 9, and it will probably misidentify Solaris 10 (unless Sun
> marketing changes Solaris names again). For example, on a Solaris 8
> box, config.guess outputs "sparc-sun-solaris2.8"; but there never was
> and never will be a "Solaris 2.8", as Solaris 2.6 (SunOS 5.6) was
> immediately followed by Solaris 7 (SunOS 5.7).
>
> The time to fix this is now long overdue. Before I do, I want to give
> plenty of warning to the GNU packages that comprise the toolchain, as
> these are typically most sensitive to the output of config.guess. Any
> objections? I have documented the change in a new config/NEWS file
> that is already committed to subversions.gnu.org.
I consider this sort of change a maintenance nightmare: suddenly all
packages that could handle all versions of Solaris 2 in the same way
(matching *-*-solaris2*) have to handle *-*-solaris2*, *-*-solaris[789] and
*-*-solaris2.1*. I see no real reason to follow Sun's marketing nonsense
in this issue, and as you already indicate, there's a `good' change that
Solaris 10 will be called differently again. All Sun employees are
talking about Solaris Next, e.g., knowing all too well that marketing will
get it's dirty fingers on this issue before FCS. I've been told that they
were very close to calling Solaris 9 something completely different.
If one really *must* change something for technical correctness, switch to
*-*-sunos5*, which will allways remain correct as has already been
indicated, i.e. whatever they happen to call Solaris 10 by the time it's
released, the O/S will be SunOS 5.10. But even this sort of change
unnecessarily confuses users and creates a maintenance burden on all users
of config.{guess, sub}.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2003-11-20 14:12 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 9:31 Ben Elliston
2003-11-20 11:34 ` Eric Botcazou
2003-11-20 14:12 ` Rainer Orth [this message]
2003-11-20 18:57 ` Paul Eggert
2003-11-20 19:14 ` Rainer Orth
2003-11-20 19:46 ` Albert Chin-A-Young
2003-11-20 21:02 ` Paul Eggert
2003-11-20 21:19 ` Rainer Orth
2003-11-21 0:33 ` Paul Eggert
2003-11-21 0:44 ` Rainer Orth
2003-11-22 21:28 ` Richard Stallman
2003-11-23 22:13 ` Branko Čibej
2003-11-24 6:33 ` Paul Eggert
2003-11-24 7:03 ` Eric Botcazou
2003-11-24 9:41 ` Paul Eggert
2003-11-24 10:01 ` Eric Botcazou
2003-11-24 20:46 ` Paul Eggert
2003-11-25 7:46 ` Eric Botcazou
2003-11-25 21:55 ` Paul Eggert
2003-11-26 5:25 ` Eric Botcazou
2003-11-26 5:34 ` Ben Elliston
2003-11-26 22:59 ` Russ Allbery
2003-11-25 4:37 ` Richard Stallman
2003-11-26 2:03 ` Zack Weinberg
2003-11-20 21:05 ` Eric Botcazou
2003-11-20 21:15 ` Rainer Orth
2003-11-20 22:27 ` Phil Edwards
2003-11-21 21:39 ` tm_gccmail
2003-11-21 21:45 ` Joe Buck
2003-11-27 10:50 ` Zack Weinberg
2003-11-28 23:22 ` Paul Eggert
2003-11-29 0:25 ` Zack Weinberg
2003-12-01 20:50 ` Paul Eggert
2003-12-01 21:29 ` Zack Weinberg
2003-12-02 21:29 ` Paul Eggert
2003-12-02 21:40 ` Zack Weinberg
2003-12-02 22:08 ` Ben Elliston
2003-12-03 17:17 ` Richard Stallman
2003-12-03 17:22 ` Zack Weinberg
2003-12-03 17:26 ` Arnaud Charlet
2003-12-04 7:33 ` Richard Stallman
2003-12-04 8:00 ` Branko Čibej
2003-12-05 17:26 ` Richard Stallman
2003-12-05 17:53 ` Zack Weinberg
2003-12-05 18:44 ` Joe Buck
2003-12-06 11:31 ` Nix
2003-12-07 23:04 ` Branko Čibej
2003-12-04 10:11 ` Zack Weinberg
2003-12-04 10:49 ` Ben Elliston
2003-12-04 21:37 ` Paul Eggert
2003-12-04 21:53 ` Zack Weinberg
2003-12-04 23:00 ` Arnaud Charlet
2003-12-04 23:04 ` Alexandre Oliva
2003-12-04 23:15 ` Joe Buck
2003-12-04 23:27 ` Zack Weinberg
2003-12-04 23:38 ` Ben Elliston
2003-12-04 23:41 ` Zack Weinberg
2003-12-05 11:44 ` Alexandre Oliva
2003-12-06 5:20 ` Eric Botcazou
2003-12-06 20:37 ` Alexandre Oliva
2003-12-06 21:16 ` Eric Botcazou
2003-12-07 9:15 ` Arnaud Charlet
2003-12-07 9:45 ` Eric Botcazou
2003-12-07 19:20 ` Zack Weinberg
2003-12-05 4:50 ` Russ Allbery
2003-12-05 11:46 ` Alexandre Oliva
2003-12-08 13:25 ` Rainer Orth
2003-12-08 22:35 ` Paul Eggert
2003-12-08 23:44 ` Rainer Orth
2003-12-08 23:51 ` Zack Weinberg
2003-12-10 0:03 ` Paul Eggert
2003-12-12 5:24 ` Alexandre Oliva
2003-12-12 5:38 ` Zack Weinberg
2003-12-12 21:26 ` Rainer Orth
2003-12-05 23:20 ` Richard Stallman
2003-12-04 14:16 ` Andrew Cagney
2003-12-02 22:47 Wolfgang Bangerth
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=yddu14z3z8z.fsf@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=binutils@sources.redhat.com \
--cc=bje@wasabisystems.com \
--cc=eggert@cs.ucla.edu \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rms@gnu.org \
/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