9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: 9fans@9fans.net
Subject: [9fans] origins of configure
Date: Thu,  9 Jul 2015 09:24:57 -0600	[thread overview]
Message-ID: <201507091524.t69FOvp2025927@freefriends.org> (raw)
In-Reply-To: <8f71c132-1b4d-4d0c-a741-d0738945f22c@email.android.com>

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.
It was inspirational for autoconf, but autoconf doesn't use any of
its code, as far as I know.

Autoconf was designed to solve real portability problems. In the late 80s
and early 90s there was a huge variety of Unix systems and it was really
hard to know what was available and what wasn't based on simple ifdefs.
The variations were bigger than Erik makes out.

Today, the scale of the problem is reduced, since we have POSIX and
also fewer systems out there. Much of the bloat in the Autotools is
from legacy. But there are still very real portability issues, especially
among some of the fringe *BSD systems. MirBSD in particular is one of
the worst, but that's another rant.

If one were to start over today, one could likely arrive at a simpler
system, but portability problems remain, and they are real.

Arnold


erik quanstrom <quanstro@quanstro.net> wrote:

> confirmed.  it's existence is due to early gnu programs fighting with
> small variations in unix and compilers.  byron's rc used a small script
> to the same effect.  but for the most part, this all could be avoided
> with careful planning and not using esoteric functions.
>
> gcc also had its own configuration step.  the header rewriting is a vestage of this system.
>
> - erik
>
>
> On Jul 9, 2015 05:31, Jeff Sickel <jas@corpus-callosum.com> wrote:
> >
> >
> > > On Jul 9, 2015, at 5:19 AM, Steve Simon <steve@quintile.net> wrote: 
> > > 
> > > FWIW: fgb did a stirling script called config which sets up some 
> > > environment and runs configure under ape. It doesn't always work but often gets close 
> > > to generating a config.h as linux intended. 
> >
> > Configure predates Linux.  That, or my memory of using it to bang my head against the perl wall in the 1980s damaged the register. 
> >
> > -jas 
> >
> > … at least you’re not using Xenix 
> >
> >
> >
> From 9fans-bounces@9fans.net  Thu Jul  9 07:52:09 2015
> X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
> 	frenzy.freefriends.org
> X-Spam-Level: 
> X-Spam-Status: No, score=0.0 required=5.0 tests=TIME_LIMIT_EXCEEDED
> 	autolearn=unavailable version=3.3.1
> X-Envelope-From: 9fans-bounces@9fans.net
> Return-Path: <9fans-bounces@9fans.net>
> X-Virus-Scanned: by MailRoute
> Date: Thu, 09 Jul 2015 06:50:06 -0700
> X-Android-Message-ID: <8f71c132-1b4d-4d0c-a741-d0738945f22c@email.android.com>
> From: erik quanstrom <quanstro@quanstro.net>
> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
> Content-Type: text/plain; charset=utf-8
> Subject: Re: [9fans] Gawk in 9front-ports
> X-BeenThere: 9fans@9fans.net
> X-Mailman-Version: 2.1.13
> Precedence: list
> Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net>
> List-Unsubscribe: <http://mail.9fans.net/options/9fans>,
> 	<mailto:9fans-request@9fans.net?subject=unsubscribe>
> List-Archive: <http://mail.9fans.net/private/9fans>
> List-Post: <mailto:9fans@9fans.net>
> List-Help: <mailto:9fans-request@9fans.net?subject=help>
> List-Subscribe: <http://mail.9fans.net/listinfo/9fans>,
> 	<mailto:9fans-request@9fans.net?subject=subscribe>
> Sender: 9fans-bounces@9fans.net
> Errors-To: 9fans-bounces@9fans.net
> X-MIME-Autoconverted: from base64 to 8bit by freefriends.org id t69Dq5Ri006148
> Status: R
>
> confirmed.  it's existence is due to early gnu programs fighting with small variations in unix and compilers.  byron's rc used a small script to the same effect.  but for the most part, this all could be avoided with careful planning and not using esoteric functions.  
>
> gcc also had its own configuration step.  the header rewriting is a vestage of this system.
>
> - erik
>
>
> On Jul 9, 2015 05:31, Jeff Sickel <jas@corpus-callosum.com> wrote:
> >
> >
> > > On Jul 9, 2015, at 5:19 AM, Steve Simon <steve@quintile.net> wrote: 
> > > 
> > > FWIW: fgb did a stirling script called config which sets up some 
> > > environment and runs configure under ape. It doesn't always work but often gets close 
> > > to generating a config.h as linux intended. 
> >
> > Configure predates Linux.  That, or my memory of using it to bang my head against the perl wall in the 1980s damaged the register. 
> >
> > -jas 
> >
> > … at least you’re not using Xenix 
> >
> >
> >
>




  reply	other threads:[~2015-07-09 15:24 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                 ` arnold [this message]
2015-07-09 15:45                   ` [9fans] origins of configure tlaronde
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=201507091524.t69FOvp2025927@freefriends.org \
    --to=arnold@skeeve.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).