This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Re: [PATCH 3/6] Reinstantiate fd range check if and only if defined _STRICT_FD_SIZE_CHECK=1
- From: Arjan van de Ven <arjan at linux dot intel dot com>
- To: chrubis at suse dot cz
- Cc: Florian Weimer <fweimer at redhat dot com>, KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Wed, 03 Apr 2013 08:35:00 -0700
- Subject: Re: Re: [PATCH 3/6] Reinstantiate fd range check if and only if defined _STRICT_FD_SIZE_CHECK=1
- References: <20130403094821 dot GA1545 at rei>
On 4/3/2013 2:48 AM, chrubis@suse.cz wrote:
Hi!
How so? _FORTIFY_SOURCE is not enabled by default. If you switch it
on, there are other (valid) uses which break.
That is simply not true. It's not turned on in glibc by default but
several build systems enable it system-wide. For example SUSE
buildservice.
... and that is done deliberately accepting that it is breaking some broken code.
if you don't want to deal with it, then don't enable it!
(and if it's for one package only, it's up to the people who added it to cflags, to
unadd it inside their specfile)