From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Silly porting fun
Date: Thu, 13 Jul 2000 00:30:39 +0100 [thread overview]
Message-ID: <200007122330.TAA10568@cse.psu.edu> (raw)
>>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.
next reply other threads:[~2000-07-12 23:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 23:30 forsyth [this message]
2000-07-12 23:46 ` Christopher Nielsen
2000-07-13 5:19 ` Randolph Fritz
-- strict thread matches above, loose matches on Subject: below --
2000-07-14 18:42 dhog
2000-07-14 14:53 Russ Cox
2000-07-14 14:04 bobf
2000-07-14 9:58 forsyth
2000-07-16 16:04 ` Lucio De Re
2000-07-14 4:18 pip
2000-07-13 23:58 rob pike
2000-07-14 9:18 ` Douglas A. Gwyn
2000-07-13 20:32 Russ Cox
2000-07-13 8:36 forsyth
2000-07-13 16:01 ` Greg Hudson
2000-07-14 9:15 ` peter huang
2000-07-14 9:19 ` Kris Van Hees
2000-07-14 14:56 ` Douglas A. Gwyn
2000-07-17 9:11 ` Christopher Browne
2000-07-13 0:31 Russ Cox
2000-07-13 5:21 ` Randolph Fritz
2000-07-13 0:23 Russ Cox
2000-07-13 0:33 ` Christopher Nielsen
2000-07-12 21:16 Randolph Fritz
2000-07-12 21:44 ` Latchesar Ionkov
2000-07-13 9:59 ` Douglas A. Gwyn
2000-07-13 0:38 ` arisawa
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=200007122330.TAA10568@cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).