On Thu, Jul 25, 2013 at 1:17 AM, Andrew Haley <a...@redhat.com> wrote: > On 07/24/2013 11:51 PM, David Starner wrote: >> On Wed, Jul 24, 2013 at 8:50 AM, Andrew Haley <a...@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.
