From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unofficial Gentoo Development Guide and Autotools
Date: Fri, 20 May 2005 07:22:15 +0100 [thread overview]
Message-ID: <20050520072215.15afb99c@snowdrop> (raw)
In-Reply-To: <20050520060612.GA10306@ols-dell.gg3.net>
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
On Fri, 20 May 2005 15:06:12 +0900 Georgi Georgiev <chutz@gg3.net>
wrote:
| - The configure script is run to produce one or Makefile files
| from Makefile.in files.
| + The configure script is run to produce
| one or more Makefile files from Makefile.in files.
Gah! I'm sure I'd already fixed that one...
| The phrase "when an option is specified" is a bit ambiguous,
| especially since it is later referred by the explanation of
| AC_ARG_WITH. I was not sure if "option" in this case means "option" as
| in "--enable-foo=OPTION". I was confused, because one paragarph before
| the example you talk about "--enable-foo and --disable-foo *switches*
| to ./configure".
.. Important:: The third argument is used when a ``--enable`` or
``--disable`` switch to ``./configure`` is provided, and the fourth
is used when such a switch is *not* passed. A common misconception is
that the third is enable and the fourth is disable -- this is **not**
the case. You may encounter packages that get this wrong.
Does that sound any better?
| - coloring
|
| %.1 : %.in
| @regex_cmd@ -e "s,\@VERSION\@,$(VERSION),g" $? > $@
|
| The first "@" is span.Special and the second one is span.Constant.
Hrm, that's a vim thing (I'm using a vim script to do the highlighting
at compile time, it's not manual). If someone enjoys pain they could
have a go at making vim's automake highlighting smarter... Don't think
I'm brave enough to touch that one myself.
Thanks,
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-20 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 3:44 [gentoo-dev] Unofficial Gentoo Development Guide and Autotools Ciaran McCreesh
2005-05-19 5:27 ` Donnie Berkholz
2005-05-19 5:43 ` Mike Frysinger
2005-05-19 12:48 ` Mike Frysinger
2005-05-19 5:48 ` Mike Frysinger
2005-05-19 12:06 ` Stephen Bennett
2005-05-19 17:53 ` Chris White
2005-05-19 18:59 ` Mike Frysinger
2005-05-19 19:06 ` Mike Frysinger
2005-05-19 19:47 ` Chris White
2005-05-19 20:14 ` Mike Frysinger
2005-05-20 5:06 ` Ciaran McCreesh
2005-05-20 6:06 ` Georgi Georgiev
2005-05-20 6:22 ` Ciaran McCreesh [this message]
2005-05-20 9:01 ` Georgi Georgiev
2005-05-20 9:29 ` Ciaran McCreesh
2005-05-20 10:11 ` Georgi Georgiev
2005-05-20 22:10 ` Ciaran McCreesh
2005-05-20 9:40 ` Georgi Georgiev
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=20050520072215.15afb99c@snowdrop \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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