From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: zack@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: Obsolete building in source dir?
Date: Wed, 15 Sep 2004 16:16:00 -0000 [thread overview]
Message-ID: <1095254892.26494.18.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <200409151308.i8FD8jjT008752@greed.delorie.com>
On Wed, 2004-09-15 at 14:08, DJ Delorie wrote:
> > If we print out 'creating build directory in <target>-build...
> > configuring in <target>-build' then it's no-longer 'behind their back'.
>
> Assuming the user catches that line in the heaping gobs of output
> configure produces (especially when builds are automated). Better to
> say:
>
> $ ./configure
> configure: Please create a separate build directory for builds including gcc.
>
> $
>
> ... so that the user KNOWS.
Why does the user have to KNOW this? Why would they care? We don't
assume that they have to know a lot of other things. All they want to
do is build the compiler so they can install it. I haven't seen a
single reason why they should care that this is done in a subdirectory
of the source rather than in the sources themselves.
R.
next prev parent reply other threads:[~2004-09-15 13:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 4:06 Giovanni Bajo
2004-09-13 7:34 ` DJ Delorie
2004-09-14 19:21 ` Joe Buck
2004-09-14 19:40 ` Zack Weinberg
2004-09-14 19:59 ` Joseph S. Myers
2004-09-14 20:12 ` DJ Delorie
2004-09-14 21:25 ` Zack Weinberg
2004-09-14 22:25 ` DJ Delorie
2004-09-26 23:05 ` Marc Espie
2004-09-28 17:38 ` Per Bothner
2004-09-15 11:09 ` Richard Earnshaw
2004-09-15 15:43 ` DJ Delorie
2004-09-15 16:16 ` Richard Earnshaw [this message]
2004-09-15 16:58 ` Phil Edwards
2004-09-15 21:15 ` Alexandre Oliva
2004-09-16 5:59 ` Ralf Corsepius
2004-09-16 16:47 ` DJ Delorie
2004-09-17 11:08 ` Ralf Corsepius
2004-09-17 21:12 ` DJ Delorie
2004-09-17 16:38 ` Alexandre Oliva
2004-09-18 15:14 ` Kai Henningsen
2004-09-18 17:31 ` Alexandre Oliva
2004-09-19 18:41 ` Kai Henningsen
2004-09-20 8:51 ` Ralf Corsepius
2004-09-16 22:01 ` Matthias B.
2004-09-14 20:08 ` DJ Delorie
2004-09-14 20:18 ` Joe Buck
[not found] ` <mailman.80195.1095191985.18468.gnu-gcc@lists.nsr.labs.mot.com>
2004-09-15 6:38 ` Loren James Rittle
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=1095254892.26494.18.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.com \
/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).