From: David Starner <prosfilaes@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>, gcc@gcc.gnu.org
Subject: Re: fatal error: gnu/stubs-32.h: No such file
Date: Fri, 26 Jul 2013 00:00:00 -0000 [thread overview]
Message-ID: <CAMZ=zj6hVKDWLuatcrOLYOiVxKhfjJ=+8wvEn0kgjGBEoi-ENw@mail.gmail.com> (raw)
In-Reply-To: <51F0DF1F.80207@redhat.com>
On Thu, Jul 25, 2013 at 1:17 AM, Andrew Haley <aph@redhat.com> wrote:
> On 07/24/2013 11:51 PM, David Starner wrote:
>> On Wed, Jul 24, 2013 at 8:50 AM, Andrew Haley <aph@redhat.com> wrote:
>>> Not at all: we're just disagreeing about what a real system with
>>> a real workload looks like.
>>
>> No, we aren't. We're disagreeing about whether it's acceptable to
>> enable a feature by default that breaks the compiler build half way
>> through with an obscure error message.
>
> No we aren't. I want that error message fixed too. A configure-
> time warning would be good.
The obscurity of the error message is only part of the problem; the
fact that it errors out halfway through a multi-hour build is also an
issue. The question is if it can't detect a compile time that this
will fail, should GCC disable multilibs?
--
Kie ekzistas vivo, ekzistas espero.
next prev parent reply other threads:[~2013-07-26 0:00 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 0:48 David Starner
2013-07-24 8:17 ` Andrew Haley
2013-07-24 8:36 ` Florian Weimer
2013-07-24 8:39 ` Andrew Haley
2013-07-24 9:05 ` Florian Weimer
2013-07-24 9:18 ` Andrew Haley
2013-07-24 10:32 ` David Starner
2013-07-24 11:14 ` Andrew Haley
2013-07-24 12:26 ` David Starner
2013-07-24 13:44 ` Andrew Haley
2013-07-24 12:37 ` Gabriel Dos Reis
2013-07-24 13:45 ` Andrew Haley
2013-07-24 15:38 ` Gabriel Dos Reis
2013-07-24 15:50 ` Andrew Haley
2013-07-24 22:52 ` David Starner
2013-07-25 8:17 ` Andrew Haley
2013-07-26 0:00 ` David Starner [this message]
2013-07-26 9:01 ` Andrew Haley
2013-07-27 13:56 ` David Starner
2013-07-27 19:23 ` Jonathan Wakely
2013-07-27 22:54 ` Gabriel Dos Reis
2013-07-27 23:10 ` David Starner
2013-07-27 23:53 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2013-07-28 13:24 FX
2013-07-29 13:06 ` FX
2013-07-29 13:23 ` Andrew Haley
2013-07-29 13:55 ` Bruce Korb
2013-07-29 14:20 ` Andrew Haley
2013-07-30 4:28 ` David Starner
2013-07-30 4:50 ` David Starner
2013-07-30 4:58 ` Andrew Pinski
2013-07-30 13:13 ` David Starner
2013-07-30 7:56 ` Andrew Haley
2013-07-30 12:52 ` David Starner
2013-07-30 14:34 ` Andrew Haley
2013-07-30 11:06 ` Michael Veksler
2013-07-30 13:54 ` FX
2013-07-31 19:44 ` Matthias Klose
2013-07-31 20:14 ` Jonathan Wakely
2013-07-31 20:23 ` Russ Allbery
2013-07-06 15:41 Bruce Korb
2013-07-06 16:02 ` Andrew Haley
2013-07-06 16:09 ` Bruce Korb
2013-07-06 18:53 ` Andreas Schwab
2013-07-07 14:00 ` Bruce Korb
2013-07-07 17:44 ` Jonathan Wakely
2013-07-07 20:33 ` Gabriel Dos Reis
2013-07-07 23:02 ` Jonathan Wakely
2013-07-08 5:17 ` Gabriel Dos Reis
2013-07-08 5:19 ` Andrew Pinski
2013-07-08 5:55 ` Gabriel Dos Reis
2013-07-08 5:59 ` Andrew Pinski
2013-07-08 6:33 ` Gabriel Dos Reis
2013-07-08 8:43 ` Andrew Haley
2013-07-08 9:00 ` Gabriel Dos Reis
2013-07-08 7:13 ` Jakub Jelinek
2013-07-08 7:18 ` Gabriel Dos Reis
2013-08-14 8:53 ` Alexandre Oliva
2013-08-14 16:39 ` Andreas Schwab
2013-08-14 19:01 ` Gabriel Dos Reis
2013-07-08 15:11 ` Bruce Korb
2013-07-08 15:24 ` Jakub Jelinek
2013-07-08 15:39 ` Bruce Korb
2013-07-08 17:27 ` Jonathan Wakely
2013-07-08 18:08 ` Bruce Korb
2013-07-16 9:40 ` Florian Weimer
2013-07-16 12:46 ` Gabriel Dos Reis
2013-07-16 13:24 ` Jonathan Wakely
2013-07-16 14:26 ` Andrew Pinski
2013-07-16 14:35 ` Bruce Korb
2013-07-16 15:04 ` Gabriel Dos Reis
2013-07-16 15:11 ` Jonathan Wakely
2013-07-16 15:13 ` Gabriel Dos Reis
2013-07-16 15:40 ` Bruce Korb
2013-07-08 8:42 ` Andrew Haley
2013-07-07 20:31 ` Gabriel Dos Reis
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='CAMZ=zj6hVKDWLuatcrOLYOiVxKhfjJ=+8wvEn0kgjGBEoi-ENw@mail.gmail.com' \
--to=prosfilaes@gmail.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).