On Oct 11, 2015, at 11:14 AM, [email protected] wrote: > Revision > 141132 > Author > [email protected] > Date > 2015-10-11 09:14:38 -0700 (Sun, 11 Oct 2015) > Log Message > > apple-gcc42: Drop support on ElCap
On Oct 11, 2015, at 11:15 AM, [email protected] wrote: > Revision > 141133 > Author > [email protected] > Date > 2015-10-11 09:15:20 -0700 (Sun, 11 Oct 2015) > Log Message > > llvm-gcc42: Drop support on ElCap On Oct 11, 2015, at 12:09 PM, [email protected] wrote: > Revision > 141134 > Author > [email protected] > Date > 2015-10-11 10:09:05 -0700 (Sun, 11 Oct 2015) > Log Message > > Refactor and update portconfigure::get_compiler_fallback > > Separate out list generation into stages for easier updates in the future. > Use newer clang versions when using libc++ as our default C++ runtime. > Don't add legacy gcc fallbacks on El Capitan. Any particular reason you removed apple-gcc42 and llvm-gcc42 on El Capitan? We only just released MacPorts 2.3.4 which finally returned apple-gcc42 and llvm-gcc42 to the list of available compilers for Xcode 6 and later (r140687). Reverting r141132, apple-gcc42 builds fine for me on 10.11, and reverting r141133, llvm-gcc42 builds fine for me with apple-gcc42 on 10.11. Are there situations where these compilers don't work correctly because of a change in El Capitan? _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
