Date: Mon, 29 Feb 2016 09:22:25 -0500 From: Brandon Allbery <allbery.b@gmail.com> To: Dewayne Geraghty <dewaynegeraghty@gmail.com> Cc: freebsd-stable stable <freebsd-stable@freebsd.org> Subject: Re: Problem with /usr/lib/libcrypt.a when building perl/python with libressl Message-ID: <CAKFCL4Uc1ZNAAWvk-2MH-aMnPF2K45STg2rHTtU0nWVJMUauoA@mail.gmail.com> In-Reply-To: <CAGnMC6q4S-U-bA2OYAZPPdLFJFJo0eBi=-wuVbKVk7k8ipjn2A@mail.gmail.com> References: <CAGnMC6q4S-U-bA2OYAZPPdLFJFJo0eBi=-wuVbKVk7k8ipjn2A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 29, 2016 at 4:05 AM, Dewayne Geraghty <dewaynegeraghty@gmail.com > wrote: > I understand the value of fPIC for shareable libraries but I'm a little > confused as to why libcrypt.a requires -fPIC; which BTW does enable both > python, perl and others to build cleanly. > Both perl and python load crypto support as shared objects associated with their respective loadable modules. As such, you can't link non-PIC static objects into those shared objects on amd64 (although it works, pretty much by accident, on i386 32-bit). -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4Uc1ZNAAWvk-2MH-aMnPF2K45STg2rHTtU0nWVJMUauoA>