Date: Sun, 8 Sep 2013 08:14:45 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: rakuco@FreeBSD.org Cc: freebsd-current@freebsd.org, kde@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous Message-ID: <20130908081445.242f77c7@thor.walstatt.dyndns.org> In-Reply-To: <201309072249.r87MnsLP052803@freefall.freebsd.org> References: <201309072249.r87MnsLP052803@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/5kI5W1PsqicJ9pw3Dt5w5KU Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 7 Sep 2013 22:49:54 GMT rakuco@FreeBSD.org wrote: > Synopsis: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: > error: call to 'swap' is ambiguous >=20 > State-Changed-From-To: open->patched > State-Changed-By: rakuco > State-Changed-When: Sat Sep 7 22:47:43 UTC 2013 > State-Changed-Why:=20 > I don't think the previous version worked. >=20 > From your description, it looks like you've switched to building with > libc++ whereas libstdc++ was being used before. >=20 > The upcoming Qt 4.8.5 plus a few patches which only made it to 4.8.6 > (but we've backported) will finally make Qt build with libc++. >=20 > We've just sent an exp-run request for Qt 4.8.5, and will hopefully > fix all these errors once it is committed. >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D181913 I build the world/kernel since early this year with=20 CXXFLAGS+=3D -stdlib=3Dlibc++ CXXFLAGS+=3D -std=3Dc++11 in /etc/src.conf. I do not use those flags in /etc/make.conf! /etc/src.conf is supposed to target ONLY the /usr/src world, not the ports - this is as I interpret the man page for /etc/src.conf and it would be logical. But this rule/thinking seems to be broken by some includes from /usr/ports/Mk ingredients. I can assure that I didn't switch anything to build the ports but rebuilding world and then restarting building. Something must have changed since then in the logic of how libc++ slipped in instead of of libstdc++. What I did was a "make delete-old-files", which deleted several GNU gcc stuff on all CURRENT boxes. I did not see that any lib got killed after I tried "make delete-old-libs". And I did not check whether libstdc++ is still being built. There are many other occasions where now c++ errors occur and I guess those ports need to be reported in one by one via PR? --Sig_/5kI5W1PsqicJ9pw3Dt5w5KU Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQEcBAEBAgAGBQJSLBXaAAoJEOgBcD7A/5N8BnAH/1BGvJpkbCIYfUV8T5Dsfw7y bHEmkEpO/DwokYVQ2DU8/q/xGPcFwAeJDozkX26Fbmi0+GJDMWrrlx/hcUInSBnL VlasAMGtH7u6UhGnLEhAW+e7pBMUEmTuDMhhYcoXcvKmdZSvmrHiReCbMyiWWZPD x8q6I1Thy2fqUZf6rmTw6dEoa8eTr0qQyVgnM4cAozw6JMlpzW9L0aj2tU0qbGpc Rc1l1DXTTGFyvoT/m//NGtClz+F1srAxr+9nR+VmrVLOLb2mEGh4eIRTgveXnbfZ AuO014D5qyY4DtNEqHn64mC/GCWLY7DIgH/Mdz8UB1A/KaP0y9Ik8b3wNA5i6ak= =Ti0P -----END PGP SIGNATURE----- --Sig_/5kI5W1PsqicJ9pw3Dt5w5KU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130908081445.242f77c7>