Bug 5853
Summary: | EGCS writing bad .o files | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | gyro |
Component: | egcs | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | gyro |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-12-07 22:36:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
gyro
1999-10-12 00:29:51 UTC
Although it is, of course, a bug for ld to dump core on any input, it does reduce the severity if this doesn't happen with egcs-1.1.2-13 and later. If you want to pursue the ld bug further I'd look at http://sourceware.cygnus.com/binutils Please submit (as an attachment in bugzilla) a self-contained test case (normally this means the output of gcc -E for a single source file along with instructions for making the problem happen). You also may want to try Red Hat Linux 6.1 (which is out for sparc as of a few days ago, on our FTP site), not that I have a specific bug fix in mind when I say that. Scott L. Burson writes: I'm sorry, I didn't explain the situation very well. I am unable to build Kerberos, period. I tried building EGCS as a further experiment, and thought it was interesting that I ran into the same problem only when I didn't apply the patches, but in retrospect this fact is probably accidental and irrelevant. It is certainly true that the bug could be in `ld' rather than `gcc', but at this point I don't see any way to know, short of manually checking the `.o' files against the ELF specification. Anyway, I'm sorry my explanation was unclear, but no, this problem is not resolved. Putting this in WORKSFORME until I have a test case (again, that would typically mean gcc -E output together with a description of what is wrong with it). ------- Email Received From "Scott L. Burson" <gyro> 12/07/99 18:13 ------- |