From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: David Given <dg@cowlark.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Building and Installing gcc-4.7.0 on Ubuntu 12.04
Date: Thu, 07 Jun 2012 00:04:00 -0000 [thread overview]
Message-ID: <CAH6eHdRMcSuFQPzPn_gr2EJ5uqjyvzbN=wLd8GNt1NJSBeteAw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdR6eaWTpVtnUXkaZP=gXyjUeGt0tCjyT5sJoxxU12u3rg@mail.gmail.com>
On 7 June 2012 01:00, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 7 June 2012 00:34, David Given wrote:
>>
>> Sure, but the build documentation still says that it should work. Given
>> that srcdir == objdir is the standard usage pattern for configure
>> scripts, I don't think anyone will be surprised that people will try it.
>>
>> This turns out not to have been the OP's problem anyway, but given the
>> wiki page you pointed them at does state clearly that srcdir == objdir
>> isn't supported, as does the FAQ entry, it would be nice if the actual
>> build documentation said it too...
>
> The wiki pages are not authoritative.
>
> One key advantage of building outside the source directory (i.e. not
> using ./configure) is that when you screw it up (and the people who
> need those docs do screw it up, in ever more innovative ways) you can
By "those docs" here I meant the wiki pages, not the official docs,
sorry that wasn't clear.
> delete the entire objdir and start again, nothing will foul up the
> srcdir if you don't build in there.
prev parent reply other threads:[~2012-06-07 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 5:49 Anup Ghatage
2012-06-06 8:00 ` Jonathan Wakely
2012-06-06 10:02 ` David Given
2012-06-06 12:17 ` Jonathan Wakely
2012-06-06 23:34 ` David Given
2012-06-07 0:00 ` Jonathan Wakely
2012-06-07 0:04 ` Jonathan Wakely [this message]
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='CAH6eHdRMcSuFQPzPn_gr2EJ5uqjyvzbN=wLd8GNt1NJSBeteAw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dg@cowlark.com \
--cc=gcc-help@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).