> On Jul 31, 2016, at 23:44, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Aug 1, 2016, at 00:44, Jeremy Huddleston Sequoia wrote: >> > >> On Jul 31, 2016, at 22:40, [ftp83plus] wrote: >>> >>> @Jeremy, I never explicitly selected clang-3.3, it is automatically >>> installed during Step 4 of >>> https://trac.macports.org/wiki/LibcxxOnOlderSystems. It is a dependency of >>> clang-3.8 and libomp. >> >> Assuming you did step 4, it shouldn't be. Your default_compilers should be >> prefering macports-clang-3.4: >> >> default_compilers macports-clang-3.4 macports-clang-3.3 gcc-4.2 >> apple-gcc-4.2 gcc-4.0 >> >> Are your default_compilers setup right? If so, can you debug why clang-3.3 >> is being used? > > I would guess it's because the libomp port lists "macports-clang-3.3" second > in compiler.whitelist after "clang".
That's not right. r150879
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users