From: David Kirkby <david.kirkby@onetel.net>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Bill Cunningham <billcun@suddenlink.net>, gcc-help@gcc.gnu.org
Subject: Re: gcc 4.6.0
Date: Tue, 07 Jun 2011 19:55:00 -0000 [thread overview]
Message-ID: <BANLkTikr2M_4=sZ146oLphXBHYROwQC4=Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikai=WJmj1QsjguBAK0AhXhEY3_kw@mail.gmail.com>
On 4 June 2011 18:56, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 4 June 2011 18:43, Bill Cunningham wrote:
>> The compilation I just did of gcc 4.6.0 seems to have worked. I did two
>> things differently. I used a build directory outside of the source
>> directory. And secondly I compiled with c++ support. I used the
>> --enable-languages=c,c++ switch also.
>>
>> I would rather have compiled without the c++ support. I don't use c++ much
>> and it took a very long time to compile. Does anyone know which two of these
>> things may have really made the difference?
>
> http://gcc.gnu.org/ml/gcc-help/2011-06/msg00066.html
>
> Do you not believe all the documentation saying that configuring
> inside the source tree might fail?
> Even when doing so causes your build to fail, and not doing so causes
> it to succeed?
>
To be honest, gcc should do what ATLAS linear algebra library does -
just refuses to build if one attempts to build in the source
directory.
Dave
prev parent reply other threads:[~2011-06-07 19:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 17:44 Bill Cunningham
2011-06-04 17:49 ` Axel Freyn
2011-06-04 17:56 ` Jonathan Wakely
2011-06-04 18:28 ` Bill Cunningham
2011-06-04 18:51 ` Jonathan Wakely
2011-06-06 21:13 ` kevin diggs
2011-06-07 0:03 ` Kai Ruottu
2011-06-07 7:54 ` Jonathan Wakely
2011-06-07 8:09 ` Jonathan Wakely
2011-06-07 19:40 ` kevin diggs
2011-06-08 6:05 ` Jonathan Wakely
2011-06-08 9:05 ` Jonathan Wakely
2011-06-08 11:09 ` Andrew Haley
2011-06-08 12:03 ` Jonathan Wakely
2011-06-08 22:14 ` kevin diggs
2011-06-09 4:26 ` Jonathan Wakely
2011-06-07 19:55 ` David Kirkby [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='BANLkTikr2M_4=sZ146oLphXBHYROwQC4=Q@mail.gmail.com' \
--to=david.kirkby@onetel.net \
--cc=billcun@suddenlink.net \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).