Date: Sun, 8 Sep 2013 22:58:25 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd-current@freebsd.org, kde@FreeBSD.org, rakuco@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: <20130908225825.6b120d6a@thor.walstatt.dyndns.org> In-Reply-To: <0F2C94E4-A544-482F-A479-B7E70D49E615@FreeBSD.org> References: <201309072249.r87MnsLP052803@freefall.freebsd.org> <20130908081445.242f77c7@thor.walstatt.dyndns.org> <0F2C94E4-A544-482F-A479-B7E70D49E615@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/ZvONgQIOUP_y6_knjJdOwnq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 8 Sep 2013 14:57:01 +0200 Dimitry Andric <dim@FreeBSD.org> wrote: > On Sep 8, 2013, at 08:14, O. Hartmann <ohartman@zedat.fu-berlin.de> > wrote: > > On Sat, 7 Sep 2013 22:49:54 GMT > > rakuco@FreeBSD.org wrote: > >=20 > >> 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 > >=20 > > I build the world/kernel since early this year with=20 > >=20 > > CXXFLAGS+=3D -stdlib=3Dlibc++ > > CXXFLAGS+=3D -std=3Dc++11 > >=20 > >=20 > > 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. >=20 > Since r255321, -stdlib=3Dlibc++ is effectively the default, at least > when you haven't set gcc as the default compiler. So it also applies > to ports, which unavoidably will lead to a bit of fallout. My > personal experience is that most C++-based ports compile fine with > libc++ instead of libstdc++, except for a few that rely on internal > libstdc++ details. >=20 > However, -std=3Dc++11 is *not* yet the default, and C++11 has different > rules here and there, so some ports might fail to compile due to this. > For some ports, too much hacking may be required to make them work > with C++11. So in case of trouble, try removing -std=3D, or setting it > to different values (c++0x, c++98, gnu++98, etc), to get the port to > compile. >=20 > Note the base system should have no problems with -std=3Dc++11, so > please continue to use the option in src.conf, and report any > problems if you encounter them, so we can fix them. :-) >=20 > -Dimitry >=20 Hello Dimitry, btw, see PR ports/181932. This is definitely NOT libc++ related. It came up since nearly all qt4-related clients (also kdelibs) fail and drop core on r255398 - they worked prior to the last update today. I tried recompiling qt4- and kdelibs4 to get my kdevelop environment as well as libreoffice back (the drop core, as well as firefox, out of the blue). I also tried compiling those ports without any settings of CXXFLAGS in /etc/src.conf, but it doens't help. I can not understand why two critical changes from different branches of the maintainig get the same time into the public (iconv/ports and libstdc++ vanishing). Maybe I'm wrong here, but after three days, two nights non-stop updating I'm through with this toy. --Sig_/ZvONgQIOUP_y6_knjJdOwnq Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQEcBAEBAgAGBQJSLOTxAAoJEOgBcD7A/5N8Ql4IAJcMGV7u/b7bG5Lm154AEkql J4MauLfy+8JSbKBtvA6mArK1huxXmKbH+LP/o2Egao0vJgQlV8IBUTGzjegAHKFn 2Qt+vL2HfGA/C1Je5UuWTyNYpaZxylUDcGiufmcubVZSDPVqoegTKdmgHPA9+5Rk 6L8sa4+ySKLsHDvGHTS/nMJ/xXY5iJkTEkQeQZUCF7B7h00w8m9NixQ0536XzeH6 aOmQ/fMsLO3nAYP9QzagHrLNBY2GetRRcyA0OgTVH+fUewQEXa5oBYqUjC03vrW/ mi4sb2nx/3lsM1PSm975M5XFGhwWoS+IlQQPpmz3QEmZAZ2W9IpxY4nIhyVx8lc= =GxfI -----END PGP SIGNATURE----- --Sig_/ZvONgQIOUP_y6_knjJdOwnq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130908225825.6b120d6a>