From: Andy Fiddaman <illumos@fiddaman.net>
To: developer@lists.illumos.org
Subject: [developer] HEADS-UP: 16892 will definitively break building with gcc 4.4 primary
Date: Mon, 18 Nov 2024 18:29:33 +0000 (UTC) [thread overview]
Message-ID: <2ab6ea48-7355-454f-8707-c91ac6bf2f4b@fiddaman.net> (raw)
Building illumos-gate using gcc 4.4 as a primary compiler hasn't been
officially supported since late 2021, but the change I'm about to integrate
is the first one I'm aware of that will definitely break this. Following
this change, the 32-bit "libast" library will not link when built with
gcc 4.4.4.
Issue: https://www.illumos.org/issues/16892
Review: https://code.illumos.org/c/illumos-gate/+/3811
I doubt anyone still cares, but I'm sending this just in case! The fix will
be to at least partially revert this change.
Andy
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Teb8715358214009f-M7a74ccd4897d0b8d5d81604d
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
next reply other threads:[~2024-11-18 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 18:29 Andy Fiddaman [this message]
2024-11-20 10:17 ` Klaus Ziegler
2024-11-20 10:25 ` Andy Fiddaman
2024-11-20 10:52 ` Klaus Ziegler
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=2ab6ea48-7355-454f-8707-c91ac6bf2f4b@fiddaman.net \
--to=illumos@fiddaman.net \
--cc=developer@lists.illumos.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;
as well as URLs for NNTP newsgroup(s).