This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/54444] New: 32-bit glibc development headers required on GNU/Linux x86_64, but not checked during configure
- From: "gerald at pfeifer dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 31 Aug 2012 23:31:42 +0000
- Subject: [Bug bootstrap/54444] New: 32-bit glibc development headers required on GNU/Linux x86_64, but not checked during configure
- Auto-submitted: auto-generated
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?