From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc@gcc.gnu.org, DJ Delorie <dj@redhat.com>
Cc: "Loren J. Rittle" <ljrittle@acm.org>
Subject: objdir == srcdir is completely unsupported
Date: Thu, 27 Jun 2002 13:39:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0206272050310.98575-100000@naos.dbai.tuwien.ac.at> (raw)
...according to our documentation, at least since:
2002-04-15 Loren J. Rittle <ljrittle@acm.org>
* doc/install.texi (Installing GCC: Configuration): Clarify
the only supported ways to configure gcc.
First, in general, GCC @strong{must} be built into a separate directory
than the sources which does @strong{not} reside within the source tree.
This is how almost all developers build GCC; building where @var{srcdir}
== @var{objdir} is completely unsupported; building where @var{objdir}
is a subdirectory of @var{srcdir} is completely unsupported.
I remember that I was a bit confused by this change and sent some message
to the list, but I failed to find further details apart from:
http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00102.html ff
Well, given recent discussions here, concerning Phil's patch which was
later reverted, I'm still confused.
Is this way of building GCC supported, or is it not? (In the former case,
we probably should change the documentation.)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next reply other threads:[~2002-06-27 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 13:39 Gerald Pfeifer [this message]
2002-06-27 14:21 ` Phil Edwards
2002-06-27 15:31 ` Loren James Rittle
2002-06-27 16:00 ` Phil Edwards
2002-06-28 0:29 ` Geoff Keating
2002-07-01 10:52 ` DJ Delorie
2002-07-02 18:16 ` Gerald Pfeifer
2002-07-02 18:25 ` DJ Delorie
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=Pine.BSF.4.44.0206272050310.98575-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ljrittle@acm.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).