From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Date: Tue, 9 May 2006 00:25:28 +0200 [thread overview]
Message-ID: <8ccc8ba40605081525p7b703dbaq318fbdb790d118d2@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620605081410j29c99b28n25bdf7843295d8f0@mail.gmail.com>
When I had to work with autoconf'd packages, I found that they worked
(most times) for platforms already considered by the package maintainers.
Auto* was a big obstacle otherwise. In general, I ended up removing most of
the #ifdef code once I found which symbols were in place for the platform I
had to cope with.
When having to deal with several platforms, I applied the same technique to
lead to different .c files for the different platforms. This worked well for me.
On 5/8/06, Jack Johnson <knapjack@gmail.com> 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
>
>
next prev parent reply other threads:[~2006-05-08 22:25 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
2006-05-08 22:25 ` Francisco J Ballesteros [this message]
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=8ccc8ba40605081525p7b703dbaq318fbdb790d118d2@mail.gmail.com \
--to=nemo@lsub.org \
--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).