Date: Wed, 13 Feb 2013 17:48:21 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: Kimmo Paasiala <kpaasial@gmail.com>, freebsd-stable@freebsd.org Subject: Re: CLANG and -fstack-protector Message-ID: <511B3E3D.5010005@ShaneWare.Biz> In-Reply-To: <20130213022215.GK99263@hades.panopticon> References: <CA%2B7WWSeFh9sJyo3kKD5wTEHoyTSjR6TuDDgDCV5Nhc_wMzVUkg@mail.gmail.com> <20130213022215.GK99263@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/02/2013 12:52, Dmitry Marakasov wrote: > afaik, in prior discussion some years ago an issue was mentioned that > some ports don't build with stack-protector, so I suggested to introduce > STACK_PROTECTOR_SAFE/_UNSAFE knobs similar to what we have for > MAKE_JOBS_SAFE_/_UNSAFE (we might actually only need > STACK_PROTECTOR_UNSAFE, as unlike MAKE_JOBS, build errors caused by > enabling stack protector are not transient, so we can have an exp-run > to just mark all uncompatible ports and consider all others compatible). > > If there's interest in this, I can refresh the patch and submit it. > I think it sounds like a good idea - I'd go with only specify unsafe when needed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?511B3E3D.5010005>