Mailinglist Archive: opensuse-packaging (249 mails)

[Guido Berhoerster <gber@xxxxxxxxxxxx>]

* Sebastian Siebert <freespacer@xxxxxx> [2010-11-21 11:02]:
> Hi again,
>
> I have identify an issue with an option "-D_FORTIFY_SOURCE=2" in the
> CFLAGS for GCC 4.x. There is a variable called "%{optflags}" in the
> spec file and it includes the option "-D_FORTIFY_SOURCE=2".
>
> The configure script try to reset the option "-D_FORTIFY_SOURCE=2"
> to "-D_FORTIFY_SOURCE=1" in CFLAGS. But the reset of CFLAGS option
> is without effect. It compile with the option "-D_FORTIFY_SOURCE=2"
> again.
>
> Now I use a sledgehammer in the spec file:
>
> export CFLAGS=`echo "$CFLAGS" | sed -e
> 's/-D_FORTIFY_SOURCE=2/-D_FORTIFY_SOURCE=1/g'`
>
> After that, everything works fine.
>
> Is there any other solution other than the sledgehammer?

Yes, check out the source code at the specified locations whether
there is a potential buffer overflow, the GCC compile time buffer
checks are activated for a reason.

-- 
Guido Berhoerster
-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx