Date: Thu, 14 Feb 2013 15:50:01 +0100 From: Pietro Cerutti <gahr@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org Subject: Re: svn commit: r40970 - head/en_US.ISO8859-1/books/porters-handbook Message-ID: <20130214145000.GN58762@gahrfit.gahr.ch> In-Reply-To: <511CF790.7040804@FreeBSD.org> References: <201302141435.r1EEZsXu042558@svn.freebsd.org> <511CF790.7040804@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2013-Feb-14, 15:41, Alex Dupre wrote: > Pietro Cerutti ha scritto: > > If a port insists on linking <literal>-lpthread</literal> > > + directly, patch it to use <literal>-pthread</literal>.</para> > > Why bother? What I have seen in some cases is that the flags are used during compilation too. In this case, using -lpthread issues a warning, while using -pthread does not. GCC, gcc: -lpthread: linker input file unused because linking not done Clang, cc: warning: -lpthread: 'linker' input unused It's more for consistency than correctness. Admittedly, I'm not everytime patching s|-lpthread|-pthread| on my PTHREAD_CFLAGS / PTHREAD_LIBS removal campaign. -- Pietro Cerutti The FreeBSD Project gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEc+ZgACgkQwMJqmJVx944gKACeIvDeA5DzISQffbeUR4frc+yE CnoAnjLaSmQXm6ebhvklbJ/H6ymezHyn =YZiW -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130214145000.GN58762>