From: David Given <dg@cowlark.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Building and Installing gcc-4.7.0 on Ubuntu 12.04
Date: Wed, 06 Jun 2012 10:02:00 -0000 [thread overview]
Message-ID: <4FCF2AA1.2000406@cowlark.com> (raw)
In-Reply-To: <CAH6eHdTVxSPpyrm6Q=Jz8DU5eE2PhsvDjtJanNRS4w6+g=tgiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Jonathan Wakely wrote:
> On 6 June 2012 06:48, Anup Ghatage wrote:
[...]
>> Untar'ed it.
>> ./configure
>
> You didn't read the docs then, see http://gcc.gnu.org/wiki/InstallingGCC
If you're referring to the need to set objdir, the documentation that
actually ships with gcc says:
> First, we highly recommend that GCC be built into a separate directory
> from the sources which does not reside within the source tree. This is
> how we generally build GCC; building where srcdir == objdir should still
> work, but doesn't get extensive testing; building where objdir is a
> subdirectory of srcdir is unsupported.
In others, it says firmly that srcdir == objdir should actually work.
Given that it doesn't, is there any chance of getting this document
changed? As it stands it's highly misleading.
--
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│ "Parents let children ride bicycles on the street. But parents do not
│ allow children to hear vulgar words. Therefore we can deduce that
│ cursing is more dangerous than being hit by a car." --- Scott Adams
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-06-06 10:02 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 [this message]
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
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=4FCF2AA1.2000406@cowlark.com \
--to=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).