Bug 194830 - lang/gcc build on 8.4 fails with gcj: internal compiler error: Killed: 9 (program jc1)
Summary: lang/gcc build on 8.4 fails with gcj: internal compiler error: Killed: 9 (pro...
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: i386 Any
: --- Affects Only Me
Assignee: Gerald Pfeifer
URL:
Keywords:
: 194831 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-11-05 09:05 UTC by RJ Angeles
Modified: 2014-11-28 19:25 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJ Angeles 2014-11-05 09:05:13 UTC
[root@phunxts01 /usr/ports/lang/gcc]# uname -a
FreeBSD phunxts01.asia.regus.local 8.4-RELEASE-p4 FreeBSD 8.4-RELEASE-p4 #0: Mon Sep  9 23:00:58 UTC 2013     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386

[root@phunxts01 /usr/ports/lang/gcc]# gcc -v
Using built-in specs.
Target: i386-undermydesk-freebsd
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]

*** ERROR ***

/build/i386-portbld-freebsd8.4/libjava/classpath/lib/classes -MT java/util/concurrent/atomic.lo -MD -MP -MF java/util/concurrent/atomic.deps @java/util/concurrent/atomic.list  -fPIC -o java/util/concurrent/.libs/atomic.o
gcj: internal compiler error: Killed: 9 (program jc1)
gcj: internal compiler error: Killed: 9 (program jc1)
no stack trace because unwind library not available
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
no stack trace because unwind library not available
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:10612: recipe for target 'java/util.lo' failed
gmake[3]: *** [java/util.lo] Error 1
gmake[3]: *** Waiting for unfinished jobs....
Makefile:10612: recipe for target 'gnu/java/nio/charset.lo' failed
gmake[3]: *** [gnu/java/nio/charset.lo] Error 1
gmake[3]: Leaving directory '/usr/ports/lang/gcc/work/build/i386-portbld-freebsd8.4/libjava'
Makefile:10217: recipe for target 'all-recursive' failed
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory '/usr/ports/lang/gcc/work/build/i386-portbld-freebsd8.4/libjava'
Makefile:13160: recipe for target 'all-target-libjava' failed
gmake[1]: *** [all-target-libjava] Error 2
gmake[1]: Leaving directory '/usr/ports/lang/gcc/work/build'
Makefile:856: recipe for target 'all' failed
gmake: *** [all] Error 2
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop in /usr/ports/lang/gcc.
*** Error code 1

Stop in /usr/ports/lang/gcc.
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2014-11-05 09:05:13 UTC
Maintainers CC'd
Comment 2 Gerald Pfeifer freebsd_committer freebsd_triage 2014-11-05 14:35:05 UTC
*** Bug 194831 has been marked as a duplicate of this bug. ***
Comment 3 Gerald Pfeifer freebsd_committer freebsd_triage 2014-11-08 02:20:09 UTC
Are you sure this is not a hardware problem (or too little RAM
or ulimit set)?

Can you disable the JAVA option, which is essentially used by a
single port, so you probably won't need it anyway?  That'll also
speed up build time.
Comment 4 Gerald Pfeifer freebsd_committer freebsd_triage 2014-11-08 17:15:42 UTC
http://portsmon.freebsd.org/portoverview.py?category=&portname=gcc&wildcard=
only shows successful builds.
Comment 5 Gerald Pfeifer freebsd_committer freebsd_triage 2014-11-23 08:29:36 UTC
I believe this is a user/machine specific issue (hardware, ulimit,...).

If it is not, please advise.
Comment 6 RJ Angeles 2014-11-24 01:42:05 UTC
Hi Gerald,

It suddenly worked when I tried it on the following day.

Anyway, Thanks a lot!
Comment 7 Alex 2014-11-27 20:14:41 UTC
I am having the same exact problem, my system is a fresh upgrade from 9.1 I am now running 10.1 and am trying to recompile all the ports... When i just try to install gcc 4.8.3 on its own i get the same exact error


Adding multilib support to Makefile in ../.././../gcc-4.8.3/libgfortran
multidirs=
with_multisubdir=
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing gstdint.h commands
gmake[3]: Leaving directory '/usr/ports/lang/gcc/work/build'
Makefile:856: recipe for target 'all' failed
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory '/usr/ports/lang/gcc/work/build'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/gcc
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/gcc



Adding multilib support to Makefile in ../.././../gcc-4.8.3/libgfortran
multidirs=
with_multisubdir=
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing gstdint.h commands
gmake[3]: Leaving directory '/usr/ports/lang/gcc/work/build'
Makefile:856: recipe for target 'all' failed
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory '/usr/ports/lang/gcc/work/build'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/gcc
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/gcc
Comment 8 Alex 2014-11-28 17:47:19 UTC
I have resolved this issue. The default configuration options for lang/gcc on the 10.1_RELEASE ports collection has BOOTSTRAP set to off. This will cause it to fail, you must change this to on.
Comment 9 Gerald Pfeifer freebsd_committer freebsd_triage 2014-11-28 19:07:50 UTC
(In reply to Alex from comment #8)
> I have resolved this issue. The default configuration options for lang/gcc
> on the 10.1_RELEASE ports collection has BOOTSTRAP set to off. This will
> cause it to fail, you must change this to on.

So you are saying that some version of clang (or systems) miscompile
GCC/GCJ?  That's unfortunate.  

Our automated testers did not run into this, nor does the majority of
users, so I am wondering what may be special about your two environments
(one of which is FreeBSD 8.4, one 10.1).  Given 8.4, it probably is not
even related to clang.
Comment 10 Alex 2014-11-28 19:25:45 UTC
(In reply to Gerald Pfeifer from comment #9)
> (In reply to Alex from comment #8)
> > I have resolved this issue. The default configuration options for lang/gcc
> > on the 10.1_RELEASE ports collection has BOOTSTRAP set to off. This will
> > cause it to fail, you must change this to on.
> 
> So you are saying that some version of clang (or systems) miscompile
> GCC/GCJ?  That's unfortunate.  
> 
> Our automated testers did not run into this, nor does the majority of
> users, so I am wondering what may be special about your two environments
> (one of which is FreeBSD 8.4, one 10.1).  Given 8.4, it probably is not
> even related to clang.

I dont think they miscompile they just have the bootstrap option set to 'No' when it should be set to 'yes'.. this is easily fixed by running make config prior to compiling it.