Date: Wed, 24 Sep 2003 01:34:13 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.org Subject: Re: Initial list of ports that fail due to -pthread Message-ID: <20030924053413.GA28722@wombat.localnet> In-Reply-To: <20030924021820.GA55388@rot13.obsecurity.org> References: <20030924021820.GA55388@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Kris Kennaway <kris@obsecurity.org> [030923 22:21]: > Here is a partial list of the ports that need to be taught to respect > PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I > just grepped for the "-pthread is deprecated" error message). None of One very important group of ports that should get looked at when this gets worked out is KDE. Apparently, Qt uses a different means of determining wether to use threading, than the ports that depend on it. The qt-using ports appear to check for -lpthread, then c++ -pthread, and if neither of those checks pass, disable threading: checking for pthread_create in -lpthread... no checking whether c++ supports -pthread... no However, Qt somehow knows that threads are supported and installs the libqt-mt version of it's libraries. The dependant ports then look for -lqt, not -lqt-mt, since they've disabled threading. I haven't updated my gcc since -pthread started working again, and this doesn't generate the typical "-pthread is deprecated" error, so I've been pulling my hair out for two days over it :) --Mike --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/cSzVCczNhKRsh48RAkb2AJ9CcpOPJnYNWrIb1nvjP1ggMJ+5EgCgx/12 kb12IGRbxKz1hC9kWImnwsU= =h1G5 -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030924053413.GA28722>