Date: Thu, 26 Apr 2012 12:45:49 +0200 From: Jeremie Le Hen <jlh@FreeBSD.org> To: Bryan Drewery <bryan@shatow.net> Cc: freebsd-hackers@freebsd.org Subject: Re: compiling ports with SSP Message-ID: <20120426104549.GA67758@felucia.tataz.chchile.org> In-Reply-To: <4F9850D9.90300@shatow.net> References: <4F4AFB53.8020503@shatow.net> <20120315223454.GA30360@felucia.tataz.chchile.org> <4F9850D9.90300@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2012 at 02:30:33PM -0500, Bryan Drewery wrote: >=20 > Something to keep an eye on is that some ports may run `file > /usr/lib/libc.so` and find that it is an ASCII text file. >=20 > As I've mentioned, I've been running with SSP in my ports for at least a > year now, and with this ld script for several months. >=20 > The only issue I've ran into is the security/openssl port is looking at > /usr/lib/libc.so to see if it is ELF or not, and due to this is falling > back on a.out binary format and then generating incorrect ASM. I think > this is going to be a pretty rare and specific case though. I'm glad to hear that the problem doesn't seem to be widespread. How many ports do you have installed? Do you have big families like X.Org, Gnome or KDE? --=20 Jeremie Le Hen Men are born free and equal. Later on, they're on their own. Jean Yanne --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iF4EAREIAAYFAk+ZJ1wACgkQKN43Aov2z5I+qQD/fetVVR+KL/YO9YnyaSEPQ/Cj FDSM67YVgHlESb5G9BkA/1KuQDqMgb0z9ALHs7oaCwYTkuJTgw3WyuRN8fSVW0U6 =eBiB -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120426104549.GA67758>