Re: installer misidentifies illumos OS
Karl Berry <[email protected]> Mon, 9 Mar 2026 15:17:57 -0600
| Newsgroups | gmane.comp.tex.live |
|---|---|
| Message-ID | <[email protected]> |
My (possibly wrong) understanding is that when Solaris 10 temporarily
became OpenSolaris (and then later illumos), it went from 10 -> 11 to
mark the difference. But then when Oracle Solaris 11 came out it also
went from 10 -> 11.
Thanks for the info. How unfortunate.
SunOS yoknapatawpha 5.11 illumos-0a457a339d i86pc i386 i86pc
SunOS matroska 5.11 omnios-r151056-1acbca4f5bd i86pc i386 i86pc
Thanks. So that should provide enough information to distinguish. But
really it would be best to make the change in config.guess. Do you have
any idea of whether there would be problems with other software if
config.guess started returning -*illumos2.11 and *omnios2.11?
It would be good to bring it up on [email protected]. It's
surprising to me that no one has brought up the problem before. It makes
me think that mostly it works to pretend illumos is solaris-2.11.
On the 32/64 bit thing, etc.:
- Without a C compiler, the result is i386-pc-solaris2.11
- With a C compiler (gcc), the result is x86_64-pc-solaris2.11
Based on yours and Nelson's checks, I'm guessing there are few if any
actual 32-bit machines still around running Solaris of any flavor? And
therefore we could just distribute 64-bit binaries (and drop the
32-bit)? And force the platform type to 64-bit regardless.
Or maybe we should drop all Solaris binaries -- I wonder if anyone is
even using current TL on Oracle Solaris.
Do you (or anyone) have any sense of how many people might be using
native TL on Oracle Solaris vs. potential users on illumos? --thanks, karl.