#30349 closed defect (fixed)
i386-mingw32-gcc @3.4.5-20060117-2 Compilation under Lion fails with Segmentation fault: 11
| Reported by: | panayotis@… | Owned by: | landonf (Landon Fuller) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.0 |
| Keywords: | lion | Cc: | justin.smith@…, noreply@…, peica@…, nerdling (Jeremy Lavergne) |
| Port: | i386-mingw32-gcc |
Description
After a clean install of Macports 2.0.0 under Lion, compilation of i386-mingw32-gcc fails with error. Attached is the error log.
Attachments (1)
Change History (11)
Changed 13 years ago by panayotis@…
comment:1 Changed 13 years ago by jmroot (Joshua Root)
| Keywords: | lion added; Lion removed |
|---|---|
| Owner: | changed from macports-tickets@… to landonf@… |
| Port: | i386-mingw32-gcc added |
Please remember to fill in the Port field and cc the maintainer.
comment:2 follow-up: 3 Changed 13 years ago by terrayi@…
It however compiles well with macports-gcc-45.
comment:3 Changed 13 years ago by justin.smith@…
Replying to terrayi@…:
It however compiles well with macports-gcc-45.
I'm not even able to get it to compile with macports-gcc-45.
sudo port select gcc mp-gcc45 Selecting 'mp-gcc45' for 'gcc' succeeded. 'mp-gcc45' is now active.
And still get the same output as OP, port is still trying to use llvm-gcc-4.2
comment:7 Changed 13 years ago by peica@…
I add
if {${configure.compiler} == "llvm-gcc-4.2"} {
configure.compiler gcc-4.2
}
into /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/cross/i386-mingw32-gcc/Portfile
and it seem to be OK.
comment:8 Changed 13 years ago by nerdling (Jeremy Lavergne)
| Cc: | snc@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Maintainer timeout. r85313.
comment:9 Changed 13 years ago by jmroot (Joshua Root)
That doesn't work on systems where there is no gcc-4.2. You have to add a dependency on apple-gcc42 in that case, and this port also doesn't build with clang. Fixed in r85380.
comment:10 Changed 13 years ago by peica@…
Sorry, I am not familiar with the port script. But it work for me.
Log file