of
+either:
+
+@itemize @bullet
+@item having 32-bit libc developer package properly installed (the exact
+name of the package depends on your distro); otherwise, you may encounter an
+error such as @samp{fatal error: gnu/stubs-32.h: No such file}
+@item building GCC as a 64-bit only
Were you waiting for further approval? If so: okay with the change
proposed by Andrew.
Thanks, committed as rev. 205802 with Andrew’s change.
FX
Am 29.07.2013 15:06, schrieb FX:
As a consensual first step toward addressing this issue, I suggest the
following patch to the doc. I hope it is clear enough, but suggestions are
obviously welcome. (I haven't even compiled the docs with it, as I'm on my
laptop with little battery.)
Given
On 31 July 2013 20:44, Matthias Klose wrote:
if you mention distribution specific packages, please add the ones needed for
some distributions. For Debian/Ubuntu this would be g++-multilib if the
architecture is multilib'ed, g++ otherwise.
That's not the package that provides gnu/stubs-32.h, is
Jonathan Wakely jwakely@gmail.com writes:
On 31 July 2013 20:44, Matthias Klose wrote:
if you mention distribution specific packages, please add the ones needed for
some distributions. For Debian/Ubuntu this would be g++-multilib if the
architecture is multilib'ed, g++ otherwise.
That's
error: gnu/stubs-32.h: No such file}
+@item building GCC as a 64-bit only compiler, by configuring with the
+option @option{--disable-multilib}
+@end itemize
+
@item GNAT
In order to build the Ada compiler (GNAT) you must already have GNAT
an
+error such as @samp{fatal error: gnu/stubs-32.h: No such file}
+@item building GCC as a 64-bit only compiler, by configuring with the
+option @option{--disable-multilib}
+@end itemize
Looks good.
This should be
Make sure you either have the 32-bit libc developer package properly
installed
hard.
OK, fine, the backup is to Google:
fatal error: gnu/stubs-32.h: No such file or directory
and have an early hit that tells you that you did not configure some 32 bit
developer package you had never heard of before. I guess that's easier
than configure tests or #error directives
On 07/29/2013 02:55 PM, Bruce Korb wrote:
On Mon, Jul 29, 2013 at 6:22 AM, Andrew Haley a...@redhat.com wrote:
There should be a better diagnostic.
If you remember, the start of this thread was:
Why is it that configure worked but stubs-32.h was not found?
That is the correct thing to
