From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Date: Mon, 8 May 2006 14:18:18 -0700 [thread overview]
Message-ID: <50C67ED8-5301-4657-9A4E-B4CA832F8581@telus.net> (raw)
In-Reply-To: <6e35c0620605081410j29c99b28n25bdf7843295d8f0@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Having been swearing at autoconf (and the code it causes) for much of
a week, I can vouch for the brain damage.
Consider that at best it returns a list of available features; some
of them are inferred by running the compiler, others by testing the
environment. Try cross-compiling with that kind of mess.
So after running configure, I get to hand-edit the resulting file and
*try* to catch all the places where autocrap checked if /dev/
something existed, because all those are guaranteed wrong (some OSes
don't have a /dev/...).
And the code people write to work around what autoconf says is at
least as evil. Python's posixmodule.c goes at least 5 levels of
ifdefs deep, with no hope of figuring out which bits are for which
platform. I'd rather just re-write the whole module.
Paul
On 8-May-06, at 2:10 PM, Jack Johnson wrote:
> On 5/8/06, LiteStar numnums <litestar@gmail.com> wrote:
>> seems. So for the half
>> our conformity test/configuration, it still wouldn't actually tell
>> me what
>> was really missing, which was
>> fun because it kept passing the thread test sections...
>
> So, it sounds like autoconf may function as intended but perhaps the
> person who wrote the test needs some help?
>
> Given that progress is likely to be evolutionary rather than
> revolutionary, what kind of system or environment do you see that has
> potential to wean people from autoconf with as minimal hassle as
> possible? If I'm engrossed in autoconf hell for whatever reason --
> say I'm the Firefox build maintainer, for instance -- what does the
> path out look like?
>
> -Jack
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEX7WbpJeHo/Fbu1wRAh9kAJ9CkTOBzkFloLezuO80YFLxD9O3FwCdGtT2
dozIyAO7PIqrLkKeuwp0Ciw=
=Q9wi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-08 21:18 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 0:26 erik quanstrom
2006-04-26 0:48 ` geoff
2006-04-26 0:54 ` Roman Shaposhnick
2006-04-26 0:53 ` Roman Shaposhnick
2006-04-26 2:15 ` Taj Khattra
2006-04-26 4:59 ` David Leimbach
2006-04-26 12:37 ` Anthony Sorace
2006-04-26 15:28 ` Rian Hunter
2006-04-26 16:39 ` Micah Stetson
2006-04-26 18:02 ` Bruce Ellis
2006-04-26 20:14 ` Micah Stetson
2006-05-08 14:50 ` Harri Haataja
2006-05-08 15:04 ` LiteStar numnums
2006-05-08 15:12 ` Charles Forsyth
2006-05-08 20:08 ` Micah Stetson
2006-05-08 20:52 ` LiteStar numnums
2006-05-08 21:10 ` Jack Johnson
2006-05-08 21:17 ` andrey mirtchovski
2006-05-08 21:18 ` Paul Lalonde [this message]
2006-05-08 22:25 ` Francisco J Ballesteros
2006-05-09 21:56 ` Dave Eckhardt
2006-05-10 0:13 ` geoff
2006-05-10 8:39 ` Lluís Batlle
2006-05-08 23:31 ` geoff
2006-05-09 1:18 ` Paul Lalonde
2006-05-09 1:39 ` quanstro
2006-05-09 2:12 ` Paul Lalonde
2006-05-09 2:20 ` quanstro
2006-05-09 3:00 ` Paul Lalonde
2006-05-09 9:32 ` Bruce Ellis
2006-04-26 22:57 ` Roman Shaposhnick
2006-04-26 4:57 ` David Leimbach
2006-04-26 4:53 ` Ronald G Minnich
2006-04-26 5:11 ` Roman Shaposhnick
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 0:45 erik quanstrom
2006-05-10 2:09 ` Lyndon Nerenberg
2006-05-10 3:35 ` David Arnold
2006-05-10 4:03 ` Lyndon Nerenberg
2006-05-08 22:02 erik quanstrom
2006-04-27 2:13 erik quanstrom
2006-04-27 1:35 erik quanstrom
2006-04-27 1:23 erik quanstrom
2006-04-27 5:08 ` Micah Stetson
2006-04-27 1:10 erik quanstrom
2006-04-27 2:06 ` Jack Johnson
2006-04-26 3:24 jmk
2006-04-26 2:38 erik quanstrom
2006-04-26 0:55 erik quanstrom
2006-04-26 1:07 ` Roman Shaposhnick
2006-04-25 10:20 erik quanstrom
2006-04-25 2:30 erik quanstrom
2006-04-25 2:48 ` Derek Fawcus
2006-04-24 20:37 Ronald G Minnich
2006-04-24 20:51 ` Charles Forsyth
2006-04-24 21:32 ` Brantley Coile
2006-04-25 11:06 ` Anthony Sorace
2006-04-25 11:08 ` Anthony Sorace
2006-04-25 2:15 ` Derek Fawcus
2006-04-25 2:23 ` Roman Shaposhnick
2006-04-25 2:37 ` Derek Fawcus
2006-04-25 3:51 ` Roman Shaposhnick
2006-04-25 8:17 ` Derek Fawcus
2006-04-25 17:53 ` Roman Shaposhnick
2006-04-26 1:11 ` Derek Fawcus
2006-04-26 1:19 ` Roman Shaposhnick
2006-04-26 2:12 ` Derek Fawcus
2006-04-25 3:02 ` Andy Newman
2006-04-25 3:13 ` Ronald G Minnich
2006-04-25 19:57 ` Dan Cross
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=50C67ED8-5301-4657-9A4E-B4CA832F8581@telus.net \
--to=plalonde@telus.net \
--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).