From: Kevin Handy <kth@srv.net>
To: Kai Henningsen <kaih@khms.westfalen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc 3.2's cpp breaks configure scripts
Date: Thu, 01 Aug 2002 12:40:00 -0000 [thread overview]
Message-ID: <3D498FA0.6030705@srv.net> (raw)
In-Reply-To: <8U0hjgPHw-B@khms.westfalen.de>
Kai Henningsen wrote:
>matz@suse.de (Michael Matz) wrote on 31.07.02 in <Pine.LNX.4.33.0207311553070.31138-100000@wotan.suse.de>:
>
>
>
>>On Wed, 31 Jul 2002, Jan-Benedict Glaw wrote:
>>
>>
>>
>>>Well... Having used autoconf/automake only _once_ myself, I can tell
>>>that it's quite hard to work with it. I've not really understood its
>>>concepts, I've not really found good/comprehensive documentation.
>>>
>>>
>>Although this gets OT quickly, autoconf and automake come with extensive
>>documentation in form of info pages.
>>
>>
>
>Yeah, but those docs are much better as a reference than as a tutorial.
>IMAO, they are pretty much useless as a tutorial.
>
>And if you look at existing uses, that certainly shows lots and lots of
>pure cargo-cult programming. I'd say that by far most autoconf users don't
>understand their tool.
>
>MfG Kai
>
>
There is a book on autoconf and automake
> http://sources.redhat.com/autobook/
It's a couple of years old though.
next prev parent reply other threads:[~2002-08-01 19:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 8:58 Jeff Garzik
2002-07-31 9:07 ` Gareth Pearce
2002-07-31 12:44 ` Joe Buck
2002-08-01 10:32 ` Phil Edwards
2002-08-01 11:15 ` Neil Booth
2002-08-01 12:31 ` Phil Edwards
2002-07-31 9:19 ` Andreas Schwab
2002-07-31 9:39 ` Jeff Garzik
2002-07-31 9:39 ` Jan-Benedict Glaw
2002-07-31 9:54 ` Michael Matz
2002-08-01 9:45 ` Kai Henningsen
2002-08-01 12:40 ` Kevin Handy [this message]
2002-08-01 9:45 ` Kai Henningsen
2002-08-01 14:47 ` Joe Buck
2002-08-08 20:39 ` Roger Corman
2002-08-09 12:07 ` Joe Buck
2002-07-31 23:52 Gareth Pearce
2002-08-01 0:03 Gareth Pearce
2002-08-01 0:07 ` Jakub Jelinek
2002-08-01 0:15 Gareth Pearce
2002-08-01 0:35 ` Jakub Jelinek
[not found] <no.id>
2002-08-01 12:02 ` John David Anglin
[not found] <200208021635.g72GZDrs008047@hiauly1.hia.nrc.ca>
2002-08-01 14:52 ` H}kan Hjort
2002-08-01 20:09 ` John David Anglin
2002-08-02 11:01 ` Bruno Haible
2002-08-02 12:29 ` John David Anglin
2002-08-02 14:42 ` Paul Eggert
2002-08-03 13:48 ` Nix
2002-08-03 14:55 ` John David Anglin
2002-08-03 15:24 ` Zack Weinberg
2002-08-03 19:34 ` Gareth Pearce
2002-08-03 14:42 ` John David Anglin
2002-08-03 15:36 ` Gabriel Dos Reis
2002-08-03 16:07 ` Zack Weinberg
2002-08-03 20:33 ` John David Anglin
2002-08-03 21:58 ` Miles Bader
2002-08-03 21:58 ` Daniel Jacobowitz
2002-08-01 16:54 Gareth Pearce
2002-08-11 10:27 John David Anglin
2002-08-12 14:40 ` Nix
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=3D498FA0.6030705@srv.net \
--to=kth@srv.net \
--cc=gcc@gcc.gnu.org \
--cc=kaih@khms.westfalen.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).