From: Alexandre Oliva <aoliva@redhat.com>
To: DJ Delorie <dj@delorie.com>
Cc: bkoz@redhat.com, gcc@gcc.gnu.org, binutils@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: srcdir == objdir build issues [SC take note]
Date: Sat, 10 May 2003 04:57:00 -0000 [thread overview]
Message-ID: <orptmrqtyq.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200305100140.h4A1eKqB022183@envy.delorie.com>
On May 9, 2003, DJ Delorie <dj@delorie.com> wrote:
> It also added a maintenance headache for the "synthetic" top-level
> Makefile, since every target in the real Makefile would have to be
> replicated
Not every target, only the standard ones, such as all, install, clean,
possibly bootstrap. Or we could just finish ./configure by printing a
message such as:
since the build instructions suggest you should build in a
directory separate from the source tree, we went ahead and
created it for you. To build, cd to that directory and then
make bootstrap or make all will work.
This will break for people who automate it with ./configure; make;
make install, but GCC has had a non-standard build procedure forever
(we recommend make bootstrap, not make), and the error may actually be
a good opportunity for people to actually read the installation
instructions. Especially if the message actually points people at
it.
Hmm... But then, why not go ahead and just fail to configure anyway.
Yeah... It makes sense as well. Maybe even more sense...
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-05-10 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 1:12 Benjamin Kosnik
2003-05-10 1:40 ` DJ Delorie
2003-05-10 4:56 ` Ian Lance Taylor
2003-05-10 4:57 ` Alexandre Oliva [this message]
2003-05-11 0:43 ` Phil Edwards
2003-05-11 0:46 ` DJ Delorie
[not found] <20EC888E-81F7-11D7-9B47-000393681B36@yahoo.com>
2003-05-09 17:55 ` DJ Delorie
2003-05-09 18:19 ` Phil Edwards
2003-05-09 18:41 ` DJ Delorie
2003-05-09 18:54 ` Phil Edwards
2003-05-09 22:35 ` Alexandre Oliva
2003-05-09 22:14 ` Neil Booth
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=orptmrqtyq.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=bkoz@redhat.com \
--cc=dj@delorie.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.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).