Opened 12 years ago
Last modified 12 years ago
#35149 new defect
arm-aout-gcc: cc1: internal compiler error: Segmentation fault: 11
Reported by: | repozitor@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.1 |
Keywords: | Cc: | ||
Port: | arm-aout-gcc |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
hi
platfrom detail:
OSX 10.7.4 (Lion) Xcode 4.2
during the installing i notice that i can't install "arm-aout-gcc"
and i try it with another command, "sudo port install arm-aout-gcc configure.compiler=llvm-gcc-4.2".
but i see error and past it on:
http://dl.dropbox.com/u/71850189/main.log
and i present it on channel, and get this detail:
"the source is trying to build a symbol name dynamically and failing. "
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-aout-gcc/arm-aout-gcc/work/gcc-3.3.6/newlib/libc/machine/arm/setjmp.S:83:26: pasting "_" and "\" does not give a valid preprocessing token"
Attachments (1)
Change History (3)
Changed 12 years ago by repozitor@…
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | Bug- arm-aout-gcc removed |
Port: | arm-aout-gcc added |
Priority: | High → Normal |
Summary: | Bug Report for "sudo port install arm-aout-gcc" → arm-aout-gcc: cc1: internal compiler error: Segmentation fault: 11 |
comment:2 Changed 12 years ago by jmroot (Joshua Root)
Thing is, the arm*-*-aout* target was declared obsolete in gcc 3.3, and removed in gcc 3.4:
Note: See
TracTickets for help on using
tickets.
I have fixed your WikiFormatting.
The main.log you linked to on Dropbox was made building with clang. As you said, it fails with:
The main.log you attached to this ticket was made with llvm-gcc-4.2. It fails with:
You could follow those instructions and report the bug to the developers of gcc, however this is gcc version 3.3.6, which is ancient in the extreme and the developers are undoubtedly no longer fixing bugs in it. We probably need to update this port to a much newer version.
Something you could try first is upgrading to the latest version of Xcode for Lion. You said you're on Xcode 4.2; 4.3.3 has been available for a month already. You can get it from the Mac App Store or Apple Developer Connection.
In any case there is no maintainer for this port in MacPorts so you're on your own in figuring out how to fix it. If you develop a patch for the Portfile that makes it work, please share it with us.