[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Archaeology time: Help me identify these ancient OSes and vendors
From: |
Zack Weinberg |
Subject: |
Archaeology time: Help me identify these ancient OSes and vendors |
Date: |
Tue, 28 May 2024 02:35:34 +0000 |
User-agent: |
Cyrus-JMAP/3.11.0-alpha0-491-g033e30d24-fm-20240520.001-g033e30d2 |
I've been trying to fill in as many gaps as possible in the config.sub
test suite (and finding a whole bunch of actual bugs in the process).
I have a short list of inputs where the actual code to handle them is
incomplete or broken, there's nothing in config.guess to use as a clue,
and I don't know what the correct canonical system name should be.
gcc@ mailing list cc:ed because I know some of you have long memories.
These are probably all either vendor or OS names from the late 1980s or
early 1990s. Can anyone help me fill out the following list of things
that ought to appear in testsuite/config-sub.data, if I knew what to
put in place of the question marks?
???-pc533 ???-pc533-???
???-sim ???-sim-???
???-ultra ???-ultra-???
???-unicom ???-unicom-???
???-acis ???-???-aos
???-triton ???-???-sysv3
???-oss ???-???-sysv3
???-storm-chaos ???-???-???
n.b. "storm-chaos" is extra troublesome because (a) it's too generic
to search for, and (b) it's being treated as a $os value but it's got
a dash in the middle, i.e. the code to handle it never got updated
for four-part canonical system names.
Thanks for any hints you can provide.
zw
- Archaeology time: Help me identify these ancient OSes and vendors,
Zack Weinberg <=