public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: "Sad Clouds" <cryintothebluesky@gmail.com>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] Binary compatibility between Illumos distributions
Date: Sun, 29 Sep 2024 16:13:19 -0400	[thread overview]
Message-ID: <17276407990.2Db2CA.652495@composer.illumos.topicbox.com> (raw)
In-Reply-To: <CAEwA5nLvg2YHzVUpb3sYdrJVktDd9OzUpBLCzGcCPGiVii3wMg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

Over the years I got frustrated with autoconf.

It is quite slow, especially on old machines like Sun Ultra 10. It could take several minutes to run autoconf scripts and then several seconds to compile some small open source package. If you are building large number of packages from something like pkgsrc, the issue is magnified significantly. Even on fast machines with many CPUs, autoconf inhibits parallelization, as it runs its tests sequentially and then many packages repeat the same tests over and over again, it is really bonkers. The issues are quite noticeable when bulk building many packages. 

It has issues correctly detecting features with cross compilers, which is why many packages cannot be cross compiled. For example, with NetBSD you can cross compile base OS on Linux, Solaris, BSD, etc. You could use the same cross compiler to cross compile pkgsrc for many other architectures, but unfortunately many packages just won't build this way.

So I try and keep it simple. I stick to POSIX and use OS name and version for specific cases where I need to resolve portability issues. I mostly link against base OS libraries, so don't need to worry too much about testing for 3rd party software.


------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/Te614dba5c9d949ba-Mbad13a6d17f4050691a54180
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 2104 bytes --]

  reply	other threads:[~2024-09-29 20:14 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
2024-09-29 20:13       ` Sad Clouds [this message]
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=17276407990.2Db2CA.652495@composer.illumos.topicbox.com \
    --to=cryintothebluesky@gmail.com \
    --cc=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).