ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous

Stefan Esser se at freebsd.org
Mon Sep 9 06:57:50 UTC 2013


Am 08.09.2013 08:14, schrieb O. Hartmann:
> On Sat, 7 Sep 2013 22:49:54 GMT rakuco at FreeBSD.org wrote:
> 
>> Synopsis: devel/qt4-script:
>> /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is
>> ambiguous
>> 
>> State-Changed-From-To: open->patched State-Changed-By: rakuco 
>> State-Changed-When: Sat Sep 7 22:47:43 UTC 2013 
>> State-Changed-Why: I don't think the previous version worked.
>> 
>> From your description, it looks like you've switched to building
>> with libc++ whereas libstdc++ was being used before.
>> 
>> 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++.
>> 
>> We've just sent an exp-run request for Qt 4.8.5, and will
>> hopefully fix all these errors once it is committed.
>> 
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=181913
> 
> 
> I build the world/kernel since early this year with
> 
> CXXFLAGS+=              -stdlib=libc++ CXXFLAGS+=
> -std=c++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.

There are ports that use bsd.prog.mk instead of the Makefile supplied
with the source files. Just grep for bsd.port.mk in the port's "files"
sub directory, if you find that /etc/src.conf settings affect a port.

I think these ports are in violation of POLA and had a longer mail
exchange with a port maintainer, who told me that use of bsd.prog.mk
was the preferred method to build binaries on FreeBSD, for base and
for ports.

So no file under /usr/ports/Mk is to blame, but some ports do
implicitly reference /etc/src.conf via their use of bsd.prog.mk.

Regards, STefan

NB: I just performed the grep suggested above and found that the
    following ports mention bsd.prog.mk in files/*:

archivers/parchive
archivers/pixz
archivers/zipmix
audio/id3v2
audio/mp3gain
benchmarks/raidtest
comms/mlan
comms/mlan3
comms/obexapp
converters/chmview
converters/iconv
devel/bcc
devel/calibrator
devel/frink
devel/libpasori
devel/linux_kdump
devel/opencvs
devel/qmake
devel/qmake4
devel/ruby-byaccr
dns/dnsreflector
editors/fb
editors/hexpert
editors/tamago
editors/tweak
emulators/cpmtools
finance/libstocks
ftp/bsdftpd-ssl
ftp/ftpsesame
games/cre
games/xroach
graphics/exiftran
graphics/s10sh
japanese/edyvalue
japanese/kon2-16dot
japanese/man
japanese/suicavalue
mail/althea
mail/archivesmtp
mail/biffer
mail/dma
math/moo
misc/cpuid
misc/team
net-mgmt/choparp
net-mgmt/icmpquery
net-mgmt/ipv6mon
net/ifdepd
net/openntpd
net/packetdrill
net/pcnfsd
net/pppd23
net/pxe-pdhcp
net/sharity-light
net/skyfish
palm/mdbconv
print/epsonepl
print/mup
security/ipv6toolkit
security/isakmpd
security/openssh-askpass
security/sst
shells/nologinmsg
shells/v7sh
sysutils/bsdmoted
sysutils/freqsdwn
sysutils/jfbterm
sysutils/sb16config
sysutils/sbniconfig
sysutils/setquota
textproc/hhm
textproc/wordnet
www/http_get
www/http_load
www/http_post
www/mathopd
www/mohawk
x11-wm/vtwm
x11/gpctool
x11/wmxss


More information about the freebsd-ports mailing list