From: Phil Edwards <pedwards@disaster.jaj.com>
To: Akim Demaille <akim@epita.fr>
Cc: gcc@gcc.gnu.org
Subject: Re: Coding convention: use of `!x' vs. `! x'
Date: Mon, 25 Sep 2000 11:32:00 -0000 [thread overview]
Message-ID: <20000925143649.B29880@disaster.jaj.com> (raw)
In-Reply-To: <mv4u2b4kfdx.fsf@nostromo.lrde.epita.fr>
On Mon, Sep 25, 2000 at 11:08:42AM +0200, Akim Demaille wrote:
>
> Would you say much of the problems are coming from the fact that the
> standards support things like
>
> ./configure
> make prefix=/foo
>
> ? I'm personally strongly in favor of deprecating this practice, and
> support only
>
> ./configure --prefix
> make
Well, but
configure --prefix=/foo
make
make prefix=/bar install
needs to be supported.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.
next prev parent reply other threads:[~2000-09-25 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <969652582.12981.ezmlm@gcc.gnu.org>
2000-09-22 17:00 ` Tim Josling
2000-09-22 18:21 ` Stan Shebs
2000-09-22 21:44 ` Mark Mitchell
2000-09-25 2:04 ` Akim Demaille
2000-09-25 7:29 ` Mark Mitchell
2000-09-25 11:32 ` Phil Edwards [this message]
2000-09-26 1:29 ` Andreas Schwab
2000-09-26 4:36 Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2000-09-22 9:32 Richard Kenner
2000-09-22 9:50 ` David Edelsohn
2000-09-22 10:22 ` Gabriel Dos Reis
2000-09-22 10:22 ` Tim Hollebeek
2000-09-30 9:52 ` Mark Mitchell
2000-09-22 0:29 Mark Mitchell
2000-09-24 22:57 ` Geoff Keating
2000-09-24 23:43 ` Mark Mitchell
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=20000925143649.B29880@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=akim@epita.fr \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).