Bug 86482 - Internal compiler error when rpmbuild --rebuild glibc
Internal compiler error when rpmbuild --rebuild glibc
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: gcc (Show other bugs)
8.0
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-23 19:40 EST by Ken MacFarlane
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-03 09:00:14 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)

  None (edit)
Description Ken MacFarlane 2003-03-23 19:40:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20030315

Description of problem:
Receive following when doing rpmbuild --rebuild --target=i586
glibc-2.3.2-4.80.src.rpm:

make[2]: Entering directory `/usr/src/redhat/BUILD/glibc-2.3.2-20030312/elf'
dynamic-link.h:167: Internal compiler error in output_die, at dwarf2out.c:6425
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[2]: ***
[/usr/src/redhat/BUILD/glibc-2.3.2-20030312/build-i586-linux/elf/dl-conflict.o]
Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.3.2-20030312/elf'



Version-Release number of selected component (if applicable):
glibc-2.3.2-4.80

How reproducible:
Always

Steps to Reproduce:
1. rpmbuild --rebuild --target=i586 glibc-2.3.2-4.80.src.rpm

    

Actual Results:  see description

Additional info:

built with gcc-3.2.2-1, glic-2.2.93-5, rpm-build-4.1-1.06
Comment 1 Ulrich Drepper 2003-04-22 04:19:03 EDT
That's a compiler error.
Comment 2 Richard Henderson 2004-10-03 09:00:14 EDT
Glibc has certainly built since then.

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