public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54444] New: 32-bit glibc development headers required on GNU/Linux x86_64, but not checked during configure
Date: Fri, 31 Aug 2012 23:32:00 -0000	[thread overview]
Message-ID: <bug-54444-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 54444
           Summary: 32-bit glibc development headers required on GNU/Linux
                    x86_64, but not checked during configure
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gerald@pfeifer.com


In the last week I twice ran into a variation of the following on two
different systems (operating systems):

In file included from /usr/include/features.h:382:0,
                 from /usr/include/stdio.h:28,
                 from /home/gp/svn/gcc-HEAD/libgcc/../gcc/tsystem.h:88,
                 from /home/gp/svn/gcc-HEAD/libgcc/libgcc2.c:29:
/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.
gmake[5]: *** [_muldi3.o] Error 1
gmake[5]: Leaving directory
`/tmp/OBJ-0901-0046/x86_64-unknown-linux-gnu/32/libgcc'

The fix is simple -- install 32-bit glibc development headers.  On openSUSE
this is in the glibc-devel-32bit package, and there are similar packages on
other distributions.

Instead of failing during the build, can we test this at configure time?


             reply	other threads:[~2012-08-31 23:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31 23:32 gerald at pfeifer dot com [this message]
2021-07-19  6:12 ` [Bug bootstrap/54444] " pinskia 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-54444-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).