From mboxrd@z Thu Jan  1 00:00:00 1970
From: forsyth@caldo.demon.co.uk
Message-Id: <200007122330.TAA10568@cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Silly porting fun
Date: Thu, 13 Jul 2000 00:30:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: d9353b6c-eac8-11e9-9e20-41e7f4b1d025

>>interested in a solution for it, since many widely-available programs
>>depend on such scripts.  A GNU "configure" script is a shell script

there is a more serious problem to many of the configure scripts
(in my experience).

having done all that probing, quite a few of them announce that
they think they know where things are but don't recognise your system anyhow.
it hasn't been named in a huge case statement.
they seemed really to be enumerating all the things they'd come across so far.
that's portability.

now i just edit the config.h to form config.h.plan9, do ape/make -n,
build a corresponding mkfile, and am done with it.
the configure doesn't usually configure properly for building several architectures
(big AND little endian) simultaneously in one directory.