fatal error: gnu/stubs-32.h: No such file

[Michael Veksler]

On 07/30/2013 07:50 AM, David Starner wrote:
> Sorry about the blank message; I accidentally hit the wrong button.
>
> On Mon, Jul 29, 2013 at 7:19 AM, Andrew Haley <aph@redhat.com> wrote:
>> It was "This is possible, but it's tricky, and it's really important
>> to get it right.  We don't want a half-arsed patch."
> We've all seen cases where a quick patch is rejected in favor of a
> hypothetical patch, and years down the road, the program still has the
> problem. The people who blocked the quick patch, naturally, never
> bothered trying to write the patch they wanted.
>
>> That's a mistranslation.  It means that there are other criteria
>> beyond some people having trouble.  Such as, we really want multilibs
>> to be built.
This is an interesting conflict of requirements. I see the point of both
sides, being a developer on one side and being a user on the other.
I really appreciate the fact that I got a clear message telling me to
install mpc. I would have hated needing to google for a cryptic error
message.

How about a middle-ground, not aiming at cross compilation?
If --enable-multilib or --disable-multilib are passed then things
are performed as today, more or less.  If these flags are not
explicitly given then gcc has to do something different:

If the system compiler is GCC then 'configure' tries if the system
GCC can build i686/x86-64/x32/etc. If the system gcc creates
workable executables then all is fine and 'configure' proceeds
to a multilib build.

Otherwise an error will be emitted saying something like:
"
   I can't figure out if your system has [???] development libraries.
   If you have [???] then rerun configure with
    --enable-multilib
If you don't have [???] then you should rerun configure with
    --disable-multilib

   You should note that if you pass --enable-multilib despite having
   no [???] development  libraries,  then you would likely get the
   following error at the last stages of bulid:
     gnu/stubs-[???].h: No such file
"

This should be relatively simple to implement, and will catch most
cases. I guess that a native English speaker can phrase something
more readable and welcoming.

Michael