Opened 13 years ago
Closed 7 years ago
#30901 closed defect (fixed)
gcc45 @4.5.3 build failure due to ICE
Reported by: | mlabrum@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.1 |
Keywords: | Cc: | ||
Port: | gcc45 |
Description
In trying to execute 'sudo port install gcc45', the following error arises:
---> Building gcc45 Error: Target org.macports.build returned: shell command failed (see log for details) Log for gcc45 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/main.log Error: Status 1 encountered during processing.
In that log file (see attached), the first error found is related to combine.c; the log file from the line on is
:info:build ../../gcc-4.5.3/gcc/combine.c: In function 'record_value_for_reg'::info:build ../../gcc-4.5.3/gcc/combine.c:11727:1: internal compiler error: Segm entation fault :info:build Please submit a full bug report,:info:build with preprocessed source if appropriate.:info:build See <http://gcc.gnu.org/bugs.html> for instructions. :info:build make[3]: *** [combine.o] Error 1 :info:build make[3]: *** Waiting for unfinished jobs....:info:build rm gcc.pod gfortran.pod :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/work/build/gcc' :info:build make[2]: *** [all-stage2-gcc] Error 2:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local _var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/work/bui ld' :info:build make[1]: *** [stage2-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/work/build' :info:build make: *** [bootstrap] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/work/build' :info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/work/build" && /usr/bin/make -j2 -w bootstrap " returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for gcc45): org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Log for gcc45 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc45/gcc45/main.log
System information: Mac OS X 10.6.8, Xcode 3.2.6
Attachments (1)
Change History (6)
Changed 13 years ago by mlabrum@…
comment:1 Changed 13 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to mww@… |
---|---|
Summary: | gcc45 @4.5.3 (lang) - shell command failed → gcc45 @4.5.3 build failure due to ICE |
Please remember to cc the maintainer.
comment:2 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Owner: | changed from mww@… to macports-tickets@… |
---|---|
Status: | new → assigned |
comment:3 Changed 7 years ago by jmroot (Joshua Root)
Is this still a problem with the current version?
comment:4 Changed 7 years ago by kencu (Ken)
I let this build overnight on my system (10.6.8 / libc++) and it finished without errors:
$ port -v installed | grep gcc45 gcc45 @4.5.4_13 (active) platform='darwin 10' archs='x86_64' date='2017-11-04T01:24:52-0700' libgcc45 @4.5.4_13 (active) platform='darwin 10' archs='x86_64' date='2017-11-04T00:34:51-0700'
on the buildbots, it has built on every system from darwin_9 PPC to darwin_16. We have blacklisted it on darwin_17+.
So this looks fixed to me.
comment:5 Changed 7 years ago by kencu (Ken)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
log file