Re: v2: The GNU C Library 2.16 release plan

[Roland McGrath <roland at hack dot frob dot com>]

> So what's the next step?
> 
> * Configurations agree to _FORTIFY_SOURCE_IF_OPT?
>   - Who would set this and where?

This is solely for the benefit of hacked compiler configurations that today
predefine _FORTIFY_SOURCE.  So they would do it the same place they do
that.  I think the distributions doing that are Gentoo and Ubuntu, so we
should get buy-in from their gcc and glibc package maintainers before
proceeding.

> * We change glibc to use _FORTIFY_SOURCE_IF_OPT?

As it's not something we'd encourage users to use directly themselves,
I think we should give it a more obscure name.

But it now occurs to me that distributions might just be able to use:

'-D_FORTIFY_SOURCE=((defined __OPTIMIZE__ && __OPTIMIZE__ > 1) ? 2 : 0)'

So let's have Mike or someone similarly interested try that out.  If it
works, then we can just advise package-builders to use that (e.g. on the
wiki somewhere) and we won't need to do anything at all in libc.  Not that
we'd advise people to break their gcc this way, but if they are going to
predefine _FORTIFY_SOURCE, that's the thing to predefine it to.  This has
the advantage that it works with all libc versions, not just a forthcoming
one.


Thanks,
Roland