Bug 522870

Summary: strange pari build failure
Product: [Fedora] Fedora Reporter: Milos Jakubicek <xjakub>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: jakub
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-22 08:39:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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.