Opened 13 years ago
Closed 13 years ago
#31709 closed defect (fixed)
configure.compiler apple-gcc40 and apple-gcc42 don't set configure.cxx
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 2.0.4 |
Component: | base | Version: | 2.0.3 |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
Port: |
Change History (3)
comment:1 follow-up: 2 Changed 13 years ago by jeremyhu (Jeremy Huddleston Sequoia)
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to jeremyhu@…:
apple-gcc40 is not a valid option for configure.compiler when using C++
Ok, I didn't know; hadn't gotten around to trying to install apple-gcc40 yet. I'm not aware of anyone needing apple-gcc40 anyway.
Mostly I just wanted the apple-gcc42 configure.cxx problem documented in a ticket, so it could be closed with the correct milestone and we wouldn't forget to put it in the changelog.
What do you propose setting it to? How about:
Setting unavailable compilers to false might be helpful...
I'm slightly worried because I know from recent experience that a libtool bug makes it fail to make dylibs when a fortran compiler is found but doesn't work (as would be the case for "false"). But I'm going to work around that in the libtool port, and if any other ports that have embedded libtools have the problem, we can deal with it then. Silently using whatever the default compiler is is probably the worse option.
comment:3 Changed 13 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
apple-gcc40 is not a valid option for configure.compiler when using C++
What do you propose setting it to? How about: