Date: Sun, 25 Oct 2009 22:01:33 +1100 From: Peter Jeremy <peterjeremy@acm.org> To: Ruslan Ermilov <ru@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src Makefile.inc1 src/gnu/lib Makefile src/gnu/lib/csu Makefile src/gnu/lib/libssp Makefile src/lib/csu Makefile.inc src/lib/libc Makefile src/lib/libstand Makefile src/lib/libthr Makefile src/libexec/rtld-elf Makefile src/release Makefile ... Message-ID: <20091025110133.GA3668@server.vk2pj.dyndns.org> In-Reply-To: <200806252138.m5PLcajG067917@repoman.freebsd.org> References: <200806252138.m5PLcajG067917@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-25 21:33:28 +0000, Ruslan Ermilov <ru@freebsd.org> wrote: > Enable GCC stack protection (aka Propolice) for userland: =2E.. I realise this is very late but this seems to break profiling, at least on i386 (see http://cakebox.homeunix.net/wordpress/?p=3D109 and bin/139052). Based on a response from kan@, the problem is that libgcov.a is built with SSP enabled but gcc defaults to SSP disabled. r197277 added a work-around for dynamic linking but profiling implies static linking. IMO, it is unreasonable for an end-user to have to change compilation flags depending on whether FreeBSD was built with or without SSP. One solution would seem to be to embed libssp_nonshared.a into all non- shared libraries when the world is built using SSP. --=20 Peter Jeremy --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkrkMA0ACgkQ/opHv/APuIdpfQCguHZWSUcetN/Fiadhse+oKCAw 2DsAoKGNo50lHRV+shvezOG69PO7YQho =Cw/x -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091025110133.GA3668>