public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Kai Ruottu <kai.ruottu@wippies.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 4.6.0
Date: Tue, 07 Jun 2011 08:09:00 -0000	[thread overview]
Message-ID: <BANLkTinoqd3WdL7__2nrcjR6BWpHxnMLQg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinOZfWv-4k+hFoNOQrTqi5=V2a5hw@mail.gmail.com>

On 7 June 2011 08:46, Jonathan Wakely wrote:
> On 6 June 2011 22:41, Kai Ruottu wrote:
>>
>> The habit to build in an subdirectory of the GCC sources is quite common
>> among the RedHat-derived distros, like CentOS :
>
> It's ok if the name of the sub-directory doesn't clash with on that
> gets created as part of the build.
>
>> So maybe you guys should start to nag to the Red Hat, CentOS etc. people
>> about their way to build GCCs...
>
> They don't ask for help with their builds.

The point is that it's unsupported.  So when people come asking for
support they should do it the supported way.

Anyway, by far the biggest problem is the "cannot compute suffix of
object files" failure due to trying to install the prerequisite libs
by hand in arbitrary places unknown to the dynamic linker.  A more
useful configure check would be to test that early on and fail with a
meaningful message.

  reply	other threads:[~2011-06-07  7:50 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 [this message]
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

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=BANLkTinoqd3WdL7__2nrcjR6BWpHxnMLQg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kai.ruottu@wippies.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).