From: "Joshua M. Clulow via illumos-discuss" <discuss@lists.illumos.org>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] Binary compatibility between Illumos distributions
Date: Sun, 29 Sep 2024 12:20:44 -0700 [thread overview]
Message-ID: <CAEwA5nLvg2YHzVUpb3sYdrJVktDd9OzUpBLCzGcCPGiVii3wMg@mail.gmail.com> (raw)
In-Reply-To: <17276373860.b4251988.20418@composer.illumos.topicbox.com>
On Sun, 29 Sept 2024 at 12:16, Sad Clouds <cryintothebluesky@gmail.com> wrote:
> OK thanks for the info. Maybe ABI was the wrong word to use, I guess I was referring to a mixture of ABI and API changes that may occur during OS major version upgrade. To give you a specific example, some of the software I work on is using thread affinity APIs to bind threads to specific CPUs. Solaris < 11.2 and Illumos only support processor_bind()which has a limitation where a thread can be bound to only one CPU, where Solaris >= 11.2 also supports processor_affinity() where a thread can be bound to multiple CPUs. I quite dislike GNU autoconf scripts and tend to extract OS name and major/minor version via uname commands in a makefile and then expose various C macros to work around API differences.
I would strongly advise feature detection instead of using versions.
I don't think anybody particularly enjoys autoconf, but in this area
they are often doing the right thing: if you care about the presence
of a specific interface, you should use some feature detection
mechanism to check for it.
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/Te614dba5c9d949ba-M5373e902a4e28bd922dbb21a
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
next prev parent reply other threads:[~2024-09-29 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 7:26 Sad Clouds
2024-09-29 18:25 ` Peter Tribble
2024-09-29 19:16 ` Sad Clouds
2024-09-29 19:20 ` Joshua M. Clulow via illumos-discuss [this message]
2024-09-29 20:13 ` Sad Clouds
2024-09-30 13:01 ` Bob Friesenhahn
2024-09-30 16:16 ` Sad Clouds
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=CAEwA5nLvg2YHzVUpb3sYdrJVktDd9OzUpBLCzGcCPGiVii3wMg@mail.gmail.com \
--to=discuss@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).