Bug 522870 - strange pari build failure
Summary: strange pari build failure
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-09-11 21:38 UTC by Milos Jakubicek
Modified: 2009-09-22 08:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-09-22 08:39:47 UTC
Type: ---

Attachments (Terms of Use)

Description Milos Jakubicek 2009-09-11 21:38:23 UTC
Description of problem:

Please have a look at the following Koji task:


At the end of the ppc64 build log (http://koji.fedoraproject.org/koji/getfile?taskID=1671069&name=build.log), there is:

{standard input}: Assembler messages:
{standard input}:13039: Warning: end of file not at end of a line; newline inserted
{standard input}:15646: Error: open CFI at the end of file; missing .cfi_endproc directive
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <http://bugzilla.redhat.com/bugzilla> for instructions.

When excluding ppc64, the build fails on out-of-memory on both F12 (http://koji.fedoraproject.org/koji/taskinfo?taskID=1671202) and F11 (http://koji.fedoraproject.org/koji/taskinfo?taskID=1671908), however, it builds fine on F10 (http://koji.fedoraproject.org/koji/taskinfo?taskID=1672002)

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


How reproducible:


Steps to Reproduce:
1. cvs co pari (provided you've already setup Fedora CVS); cd pari
2. make scratch-build

Comment 1 Jakub Jelinek 2009-09-22 08:39:47 UTC
Builds just fine on both ppc64 and x86_64 with gcc-4.4.1-15, could be related to http://gcc.gnu.org/PR41101.  Anyway, there is nothing strange on the ppc64 error above, if you build with -pipe and cc1 is killed by the kernel (OOM), the assembler can report all kinds of errors, as the pipe is closed somewhere in the middle of the assembler file.

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