[Bug bootstrap/57900] New: /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[Bug bootstrap/57900] New: /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[woodard at redhat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

            Bug ID: 57900
           Summary: /usr/include/gnu/stubs.h:7:27: fatal error:
                    gnu/stubs-32.h: No such file or directory
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: woodard at redhat dot com

This is an easy problem to solve and there are a couple of ways to solve it.
The underlying problem is that I don't have one of the glibc-devel packages
installed or I can build with --disable-multilib However, I would argue that
autoconf/configure should have picked this up in much the same way that it
picks up the fact that GMP, MPFR and MPC may be missing and prints out:

configure: error: Building GCC requires GMP 4.2+, MPFR 2.3.1+ and MPC 0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at
ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
http://gcc.gnu.org/install/prerequisites.html for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

--- error text ---

/home/ben/Work/gcc/host-x86_64-unknown-linux-gnu/gcc/xgcc
-B/home/ben/Work/gcc/host-x86_64-unknown-linux-gnu/gcc/
-B/home/ben/Work/gcc-test/x86_64-unknown-linux-gnu/bin/
-B/home/ben/Work/gcc-test/x86_64-unknown-linux-gnu/lib/ -isystem
/home/ben/Work/gcc-test/x86_64-unknown-linux-gnu/include -isystem
/home/ben/Work/gcc-test/x86_64-unknown-linux-gnu/sys-include    -g -O2 -m32 -O2
 -g -O2 -DIN_GCC   -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem
./include   -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector   -fpic -mlong-double-80 -I. -I.
-I../../../host-x86_64-unknown-linux-gnu/gcc -I../../.././libgcc
-I../../.././libgcc/. -I../../.././libgcc/../gcc -I../../.././libgcc/../include
-I../../.././libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS 
-DUSE_TLS -o _gcov.o -MT _gcov.o -MD -MP -MF _gcov.dep -DL_gcov -c
../../.././libgcc/libgcov.c
In file included from /usr/include/features.h:399:0,
                 from /usr/include/stdio.h:27,
                 from ../../.././libgcc/../gcc/tsystem.h:87,
                 from ../../.././libgcc/libgcov.c:27:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or
directory
 # include <gnu/stubs-32.h>
                           ^
compilation terminated.
make[5]: *** [_gcov.o] Error 1
make[5]: Leaving directory
`/home/ben/Work/gcc/x86_64-unknown-linux-gnu/32/libgcc'
make[4]: *** [multi-do] Error 1
make[4]: Leaving directory `/home/ben/Work/gcc/x86_64-unknown-linux-gnu/libgcc'
make[3]: *** [all-multi] Error 2
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/home/ben/Work/gcc/x86_64-unknown-linux-gnu/libgcc'
make[2]: *** [all-stage1-target-libgcc] Error 2
make[2]: Leaving directory `/home/ben/Work/gcc'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/ben/Work/gcc'
make: *** [bootstrap] Error 2

[Bug bootstrap/57900] /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[woodard at redhat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|minor                       |trivial

[Bug bootstrap/57900] /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|trivial                     |enhancement

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It is hard to figure out if you have the 32bit libraries/headers installed as
the host compiler might not be able to compile 32bits but the newly compiled
compiler can.

[Bug bootstrap/57900] /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[schwab@linux-m68k.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
It's the target compiler that matters, so this check must be performed in the
target libraries.

[Bug bootstrap/57900] /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
See the long thread starting at http://gcc.gnu.org/ml/gcc/2013-07/msg00075.html

If it's easy to solve I'm sure a patch would be welcomed :)

[Bug bootstrap/57900] /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

[gdr at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57900

Gabriel Dos Reis <gdr at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gdr at gcc dot gnu.org

--- Comment #4 from Gabriel Dos Reis <gdr at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> See the long thread starting at
> http://gcc.gnu.org/ml/gcc/2013-07/msg00075.html
> 
> If it's easy to solve I'm sure a patch would be welcomed :)

In this specific case, the ease of developing a patch is to be dissociated from
a willingness to accept that it is a problem.