Opened 12 years ago
Last modified 8 years ago
#36981 assigned defect
gcc ports may not be UsingTheRightCompiler
Reported by: | udbraumann | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia), cooljeanius (Eric Gallager) | |
Port: | libstdcxx |
Description
This is a fork from Ticket #36611: libstdcxx fails to build
At present, none of the compilers installed on my system can build libstdcxx:
$ sudo port select --list gcc Available versions for gcc: apple-gcc42 gcc40 gcc42 llvm-gcc42 mp-gcc45 (active) none
As mp-gcc45 is the newest of them, I here document how it fails (main.log, config.log). To me, it seems as if some configuration problems have occured:
Some snips from config.log:
xgcc: error: unrecognized command line option '-V' xgcc: fatal error: no input files compilation terminated.
xgcc: error: unrecognized command line option '-qversion' xgcc: fatal error: no input files compilation terminated.
xgcc: internal compiler error: Segmentation fault (program cc1)
Thanks for any assistance!
Attachments (2)
Change History (8)
Changed 12 years ago by udbraumann
Changed 12 years ago by udbraumann
Attachment: | config.log added |
---|
comment:1 follow-up: 2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | jeremyhu@… added; mww@… removed |
---|---|
Owner: | changed from macports-tickets@… to mww@… |
Port: | mp-gcc47 removed |
comment:2 follow-up: 3 Changed 12 years ago by udbraumann
Replying to ryandesign@…:
We don't especially support changing the compiler. If the port fails to build with the default compiler, then of course we want to know about that.
I am very sorry, but now building libstdcxx with gcc4.0 (default) works. I have no idea why, in between I just have made a disk maintenance, and also I have used the select command of port to explicitly set gcc4.0 as default (previously, gcc had been set to "none"):
$ sudo port select --set gcc gcc4.0
Is either one of these actions likely to have solved my problem?
Thanks, this Ticket can be closed now, I think.
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to braumann@…:
I have no idea why, in between I just have made a disk maintenance, and also I have used the select command of port to explicitly set gcc4.0 as default (previously, gcc had been set to "none"):
$ sudo port select --set gcc gcc4.0Is either one of these actions likely to have solved my problem?
On Leopard with MacPorts 2.1.x, having "gcc-4.0" selected for gcc is the same as selecting "none". (With MacPorts 2.2, this will change to "gcc-4.2".) Any of those should be fine. You showed above that you had previously selected "mp-gcc45"; this might have caused the problem, if the libstdcxx configure process is not UsingTheRightCompiler.
comment:4 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Summary: | libstdcxx fails building on a 10.5.8 PPC → gcc ports may not be UsingTheRightCompiler |
---|
comment:6 Changed 8 years ago by mf2k (Frank Schima)
Owner: | mww@… deleted |
---|---|
Status: | new → assigned |
See #53012.
We don't especially support changing the compiler. If the port fails to build with the default compiler, then of course we want to know about that.