9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] origins of configure
Date: Thu,  9 Jul 2015 17:45:57 +0200	[thread overview]
Message-ID: <20150709154557.GA2875@polynum.com> (raw)
In-Reply-To: <201507091524.t69FOvp2025927@freefriends.org>

On Thu, Jul 09, 2015 at 09:24:57AM -0600, arnold@skeeve.com wrote:
> So, the history is more than this.
>
> Larry Wall's Configure (capital C) for rn and Perl was the first step
> at a shell script to examine system features and generate a config.h.

Using a shell script to generate commands to compile on diverging Unices
was, by the date, already used in G.R.A.S.S. from C.E.R.L. and this
predates Perl and so on. I guess it is not the only example.

>[...]
> Autoconf was designed to solve real portability problems.

There are two problems with the autotools stuff:

1) Features are fixed for OSes, but the configuring is done other and
other again for every program. What a system offers shall be known; and
what the developers require shall be known too. Autotools was designed
in a world where neither the OS nor the developers exactly know what
they use;

2) Cross-compilation was not in mind, with some features tested by
compiling and running programs. The result is that the majority of
software built with autotools needs to be compiled natively (even
installed on an equal system since the layout is searched on the
building node);

3) To try to understand what's going on with several steps and huge
configs is out of reach.

Rule: when it takes less time to build a solution from scratch than to
try to understand how to _use_ an existing solution (not to mention
understand), this solution has to be safely stored in /dev/null.

Note: I have put my money where my mouth is : I have built such a
solution: the one publicly used with kerTeX---but it is a side
effect, it was not meant to be released.  And it solves the 1) and
2) and solves too the space problem: when an object is not any
longer necessary, it can be automatically removed, limiting the
space needed to compile to the bare minimum.

--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                     http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2015-07-09 15:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  2:37 [9fans] Gawk in 9front-ports Jens Staal
2015-07-07 12:27 ` arnold
2015-07-07 15:25   ` Jens Staal
2015-07-07 15:45     ` Charles Forsyth
2015-07-08 12:48       ` Jens Staal
2015-07-07 21:56 ` erik quanstrom
2015-07-07 22:36   ` Kurt H Maier
2015-07-08  1:47 ` Hugo Rivera
2015-07-08  6:22   ` arnold
2015-07-08 20:05     ` Hugo Rivera
2015-07-09  8:49       ` arnold
2015-07-09  9:58         ` Jens Staal
2015-07-09 10:19           ` Steve Simon
2015-07-09 12:31             ` Jeff Sickel
2015-07-09 13:50               ` erik quanstrom
2015-07-09 15:24                 ` [9fans] origins of configure arnold
2015-07-09 15:45                   ` tlaronde [this message]
2015-07-09 18:11                     ` arnold
2015-07-09 12:57             ` [9fans] Gawk in 9front-ports Jens Staal
2015-07-09 12:33         ` Hugo Rivera

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=20150709154557.GA2875@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).