Date: Tue, 3 Feb 2015 22:21:14 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: Gleb Kurtsou <gleb@freebsd.org> Cc: Jeremie Le Hen <jlh@FreeBSD.org>, freebsd-current@freebsd.org Subject: Re: libc.so dependency on libssp_nonshared.a Message-ID: <3DB0C643-31FE-44D6-8AB4-4CE007062C55@gmail.com> In-Reply-To: <20150203074709.GA1091@reks> References: <20150201202413.GA2132@reks> <CAGSa5y0LFURkF2urpuDWXxib65qxF7a-5ZYA_SU_YOfU_h=GGg@mail.gmail.com> <20150203074709.GA1091@reks>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_3BB99CA0-506E-49B2-BFF5-F2CCFE22528E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Feb 2, 2015, at 23:47, Gleb Kurtsou <gleb@freebsd.org> wrote: > On (02/02/2015 17:06), Jeremie Le Hen wrote: >> Hi Gleb, >> On Sun, Feb 1, 2015 at 9:24 PM, Gleb Kurtsou <gleb@freebsd.org> = wrote: >>> I came across some build issues in libc.so and SSP. >>>=20 >>> libc.ldscript (aka libc.so) unconditionally includes = @@LIBDIR@@/libssp_nonshared.a >>>=20 >>> libssp* are not built if WITHOUT_SSP defined. >>>=20 >>> ObsoleteFiles.inc doesn't mention libssp*. >>>=20 >>> Consider WITHOUT_SSP=3Dyes case. As soon as one does clean = installworld >>> and/or removes stale libssp_nonshared.a ld fails to link anything >>> because of missing libssp_nonshared.a >>=20 >> I think nowadays it would make sense to get it of WITHOUT_SSP >> altogether. This will turn this into a non-issue. >=20 > Do you mean building libssp_nonshared unconditionally? It makes = perfect > sense. The library is a single stub function. >=20 > By building libssp* conditionally we may expect that -fstack-protector > complier option won't work. I wasn't able to reproduce this potential > problem. libc provides __stack_chk_fail and __stack_chk_guard. And I > failed to create a test case that would generate code using anything > like __memcpy_chk. >=20 > Perhaps we should change MK_SSP to operate as documented (add > -fstack-protector to CFLAGS) and consider adding MK_SSP_SUPPORT option > for libraries. Although there is no reason to have MK_SSP_SUPPORT if > that would imply failure to run binaries or compile with > -fstack-protector. Silly question: shouldn=92t libc.ldscript be built, conditionally with = libssp_nonshared.a? Doing that would be trivial=85 Are there any = concerns with doing this? --Apple-Mail=_3BB99CA0-506E-49B2-BFF5-F2CCFE22528E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJU0bpaAAoJEMZr5QU6S73erTcH/0PNYosODssohyO77gp6bgTQ DI5cfSwxdDlsCXzm/atsyIkFR/vxn1qAaE2dGZ0y5NYsxwGXyEkdLQ0QPY2Xy1/Q tcZnmHY6P40DitVQLg35BwB+kOIMRgGA8rt50AuW2KswXrGkTWjzRjPOqU0uypSB GTe4fBlq2W4nEBQb4oHBipmi97dT949KvveR4t5wOGURn4zREm4JfyjQfdPX2hg7 px/+jmn4X5w/4H6ZhMUPA4yg2LBaxtAQqva6NuJ3nbWMmb4P/pXVudfNHF7G6SLv gZR7WuCUDmUwL2etoAhwXAvmuSIyPOY2eJxDCuel5HEXj6B80WkMKuyyfoVfZCI= =atbj -----END PGP SIGNATURE----- --Apple-Mail=_3BB99CA0-506E-49B2-BFF5-F2CCFE22528E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB0C643-31FE-44D6-8AB4-4CE007062C55>