It was not so much intentional breakage as a reflection of what was happening anyway. By default, qmake (the build system of qtwebkit) ignores the MacPorts build environment. Some care must be taken to mimic what MacPorts expects.
Prior to the recent changes, you were probably building qtwebkit with libc++ whether you intended to or not. Example 1: Prior to http://trac.macports.org/changeset/144445, qmake compiled source code with -mmacosx-version-min=10.7, which then forced the use of libstdc++ (see http://trac.macports.org/ticket/50249). So svn2git was using libstdc++ regardless of the value of ${configure.cxx_stdlib} Example 2: qtwebkit uses CONFIG+=c++11, and qmake responds by still using -mmacosx-version-min=10.7 but also adding -std=libc++. Again, the value of ${configure.cxx_stdlib} was ignored. I inadvertently tried to build qtwebkit with libstdc++ and received predictable errors (not std::move, etc.) So now you get an error instead of silently installing software in a way you did not expect. I suppose that is progress of a sort. -Marcus > On Jan 11, 2016, at 1:50 PM, Mojca Miklavec <mo...@macports.org> wrote: > > Hi, > > I have the following port installed: > qt5-qtwebkit @5.5.1_2 (active) > > But after > http://trac.macports.org/changeset/144467/trunk/dports/aqua/qt5 > it no longer compiles: > Error: qt5-qtwebkit does not support your selected MacPorts C++ > runtime. libc++ must be selected and C++-based ports built against it. > > I know that libstdc++ is a ticking bomb (I still believe that it would > be great to officially support libc++ with the buildbots), but > nevertheless: is this recent "breakage" intentional? > > Mojca > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
