public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "woodard at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/57900] New: /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
Date: Mon, 15 Jul 2013 16:51:00 -0000	[thread overview]
Message-ID: <bug-57900-4@http.gcc.gnu.org/bugzilla/> (raw)

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


             reply	other threads:[~2013-07-15 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 16:51 woodard at redhat dot com [this message]
2013-07-15 16:52 ` [Bug bootstrap/57900] " woodard at redhat dot com
2013-07-15 16:58 ` pinskia at gcc dot gnu.org
2013-07-15 17:08 ` schwab@linux-m68k.org
2013-07-15 17:38 ` redi at gcc dot gnu.org
2013-09-01 13:30 ` gdr at gcc dot gnu.org

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=bug-57900-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).