Bug 162428 - internal compiler error: in define__GNUC__, at c-cppbuiltin.c:314
internal compiler error: in define__GNUC__, at c-cppbuiltin.c:314
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
3
sparc64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-04 10:14 EDT by Dominik Mierzejewski
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-04 10:37:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Full rpmbuild build.log (194.82 KB, text/plain)
2005-07-04 10:16 EDT, Dominik Mierzejewski
no flags Details

  None (edit)
Description Dominik Mierzejewski 2005-07-04 10:14:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
When trying to build the latest gcc version from Fedora Core 3 Updates, gcc fails to build itself (in /make bootstrap-lean/) and bails out with

<built-in>:1: internal compiler error: in define__GNUC__, at c-cppbuiltin.c:314

The command I'm using is:
sparc32 rpmbuild --rebuild gcc-3.4.3-22.fc3.src.rpm
Log attached.

Version-Release number of selected component (if applicable):
gcc-3.4.2-6.fc3.sparc

How reproducible:
Always

Steps to Reproduce:
1. rpmbuild --rebuild gcc-3.4.3-22.fc3.src.rpm
2. 
3.
  

Actual Results:  Build doesn't complete. GCC bails out with an ICE.

Expected Results:  Build should produce a new working gcc RPM.

Additional info:

Hardware:
Sun Ultra10, 440MHz UltraSparc IIi (Sabre), 256MB RAM
OS:
AuroraLinux 2.0 (Kashmir FC3)

Last few lines of build.log:
[...]
mkinstalldirs='/bin/sh ../../gcc/mkinstalldirs' \
  /bin/sh mklibgcc > tmp-libgcc.mk
mv tmp-libgcc.mk libgcc.mk
TARGET_CPU_DEFAULT="" \
HEADERS="ansidecl.h" DEFINES="" \
/bin/sh ../../gcc/mkconfig.sh tconfig.h
./xgcc -B./ -B/usr/sparc64-redhat-linux/bin/ -isystem /usr/sparc64-redhat-linux/include -isystem /usr/sparc64-redhat-linux/sys-include -L/home/staff/rathann/build/BUILD/gcc-3.4.3-20050228/obj-sparc64-redhat-linux/gcc/../ld -O2 -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include   -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-unit-at-a-time `if test x$( ./xgcc -B./ -B/usr/sparc64-redhat-linux/bin/ -isystem /usr/sparc64-redhat-linux/include -isystem /usr/sparc64-redhat-linux/sys-include -L/home/staff/rathann/build/BUILD/gcc-3.4.3-20050228/obj-sparc64-redhat-linux/gcc/../ld  -print-multi-os-directory) = x../lib64; then echo -mcmodel=medany; fi` \
   -c ../../gcc/crtstuff.c -DCRT_BEGIN \
  -o crtbegin.o
<built-in>:1: internal compiler error: in define__GNUC__, at c-cppbuiltin.c:314
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory `/var/local/rathann/build/BUILD/gcc-3.4.3-20050228/obj-sparc64-redhat-linux/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/var/local/rathann/build/BUILD/gcc-3.4.3-20050228/obj-sparc64-redhat-linux/gcc'
make: *** [bootstrap-lean] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.29993 (%build)
Comment 1 Dominik Mierzejewski 2005-07-04 10:16:15 EDT
Created attachment 116329 [details]
Full rpmbuild build.log

This is the result of:
sparc32 rpmbuild -bb gcc34.spec 2>&1 | tee build.log
Comment 2 Jakub Jelinek 2005-07-04 10:37:27 EDT
You can't put non-digits other than dot into gcc's %{release}.
Or alternatively you must ensure it doesn't make its way into version.c.
Comment 3 Dominik Mierzejewski 2005-07-05 10:20:41 EDT
Indeed, that fixes it. Still, the error message is very uninformative. Thanks.

Note You need to log in before you can comment on or make changes to this bug.