Opened 9 years ago

Closed 4 years ago

#49089 closed defect (fixed)

gcc5 @5.2.0: fatal error: ld terminated with signal 11 [Segmentation fault]

Reported by: betrussell23@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), chrstphrchvz (Christopher Chavez)
Port: gcc5

Description

Guys,

Gcc5.2 build fails with a segmentation fault. I've 2GB RAM and Core 2 duo processor.

Find attached the error log. Comprehensive log is as follows,

macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/gcc-5.2.0/gcc/build -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/gcc-5.2.0/gcc/../include  -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/gcc-5.2.0/gcc/../libcpp/include  \
		-o build/genopinit.o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/gcc-5.2.0/gcc/genopinit.c
collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
compilation terminated.
make[3]: *** [build/gencheck] Error 1
make[3]: *** Waiting for unfinished jobs....
rm gfortran.pod gcc.pod
make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/build'
make: *** [bootstrap] Error 2
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/build'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/work/build" && /usr/bin/make -j2 -w bootstrap
Exit code: 2
Error: org.macports.build for port gcc5 returned: command execution failed
Warning: targets not executed for gcc5: org.macports.activate org.macports.build org.macports.destroot org.macports.install
Error: Failed to install gcc5
Please see the log file for port gcc5 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc5/gcc5/main.log
Error: The following dependencies were not installed: py34-matplotlib py34-numpy gcc5 py34-cython cython_select py34-nose nosetests_select py34-setuptools py34-parsing py34-pyobjc-cocoa py34-pyobjc py34-py2app py34-macholib py34-modulegraph py34-altgraph py34-tornado py34-certifi qhull py34-yaml libyaml
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py34-nltk failed

Attachments (1)

gcc52_error.log (3.3 MB) - added by betrussell23@… 9 years ago.

Change History (6)

Changed 9 years ago by betrussell23@…

Attachment: gcc52_error.log added

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added; betrussell23@… removed
Keywords: gcc5.2 removed
Owner: changed from macports-tickets@… to mww@…
Port: gcc5 added; py34-nltk removed
Summary: gcc5.2 build fails with segmentation faultgcc5 @5.2.0: fatal error: ld terminated with signal 11 [Segmentation fault]

comment:2 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)

Owner: changed from mww@… to macports-tickets@…
Status: newassigned

comment:3 Changed 4 years ago by chrstphrchvz (Christopher Chavez)

gcc5 is now at 5.5.0_5, and according to https://ports.macports.org/port/gcc5/summary builds fine on macOS 10.6. Is this ticket still relevant or can it be closed?

comment:4 Changed 4 years ago by chrstphrchvz (Christopher Chavez)

Cc: chrstphrchvz added

comment:5 Changed 4 years ago by kencu (Ken)

Resolution: fixed
Status: assignedclosed

somewhere along the way, this was fixed

Note: See TracTickets for help on using tickets.