RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 822456 - g++: Internal error: Killed (program cc1plus) durring LibreOffice build
Summary: g++: Internal error: Killed (program cc1plus) durring LibreOffice build
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gcc
Version: 6.3
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-17 11:52 UTC by Tomas Pelka
Modified: 2012-05-17 11:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-17 11:57:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
build log (121 bytes, text/plain)
2012-05-17 11:52 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2012-05-17 11:52:02 UTC
Created attachment 585198 [details]
build log

Description of problem:
full log at http://nest.test.redhat.com/mnt/qa/scratch/ibm-z10-13/2012:12592/tps/libreoffice-3.4.5.2-14.el6.src.rpm-s390x-rebuild.log

Version-Release number of selected component (if applicable):
gcc-gfortran-4.4.6-4.el6.s390x
libgcc-4.4.6-4.el6.s390x
gcc-4.4.6-4.el6.s390x
gcc-c++-4.4.6-4.el6.s390x
gcc-java-4.4.6-4.el6.s390x

How reproducible:
100%

Steps to Reproduce:
1. rpmbuild --rebuild   --define "dist .el6" --define '_topdir /usr/src/redhat' --target=s390x --rcfile /tmp/tps_rpmrc_U0tdgV /mnt/redhat/brewroot/packages/libreoffice/3.4.5.2/14.el6/data/signed/fd431d51/src/libreoffice-3.4.5.2-14.el6.src.rpm
2.
3.
  
Actual results:
-----------------------------------------------------------------------
        Oh dear - something failed during the build - sorry !
  For more help with debugging build errors, please see the section in:
            http://wiki.documentfoundation.org/Development

  internal build errors:

ERROR: error 65280 occurred while making /usr/src/redhat/BUILD/libreoffice-3.4.5.2/sal/qa/OStringBuffer

 it seems that the error is inside 'sal', please re-run build
 inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------

Expected results:
should be builded

Additional info:

Comment 1 Jakub Jelinek 2012-05-17 11:57:20 UTC
Just retry, killed means OOM kill, which could very well be because multiple memory hungry builds were scheduled at the same time on the same box, or it has too few memory.  Nothing gcc can do about it, unless you get the same each time on the same source and gcc is unreasonable amounts of RAM compared to the input.


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