Date: Tue, 28 Feb 2006 16:35:12 -0500 From: Mikhail Teterin <mi+mxe@aldan.algebra.com> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@FreeBSD.org, gnome@FreeBSD.org, obrien@FreeBSD.org Subject: Re: While we discuss libtool (-fpic vs. -fPIC) Message-ID: <1141162512.20664.96.camel@mteterin.us.murex.com> In-Reply-To: <20060228213131.GB86137@xor.obsecurity.org> References: <1141151381.20664.19.camel@mteterin.us.murex.com> <20060228192453.GA84695@xor.obsecurity.org> <1141155894.20664.59.camel@mteterin.us.murex.com> <20060228195014.GA85269@xor.obsecurity.org> <1141156556.20664.66.camel@mteterin.us.murex.com> <20060228201124.GA85491@xor.obsecurity.org> <1141158688.20664.82.camel@mteterin.us.murex.com> <20060228204406.GA86137@xor.obsecurity.org> <1141159754.20664.89.camel@mteterin.us.murex.com> <20060228213131.GB86137@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=F5 =D7=D4, 2006-02-28 =D5 16:31 -0500, Kris Kennaway =D0=C9=DB=C5: > In fact I'd say none will (except those that might break by having it > defined unexpectedly), because any port that needs to define -DPIC > that in order to conditionally compile PIC code must already be doing > so, or it'd be broken out of the box. Well being 100% correct is better, than being 99.99% correct. As I said, these things aren't worth the trouble of chasing individual ports, but making something like libtool DTRT is a good idea. This includes both, `-fpic' and `-DPIC' flags. Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1141162512.20664.96.camel>