On Mon, Oct 21, 2013 at 6:33 PM, Kay Sievers <[email protected]> wrote: > On Mon, Oct 21, 2013 at 6:11 PM, Zbigniew Jędrzejewski-Szmek > <[email protected]> wrote: > >>> Hmm, I'm running up-to-date F20, from today here. And have no issues. >>> Tried a "git clean"? >> >> I now did a 'yum update', and with a bunch of packages installed, most >> notably gcc-4.8.2, this problem is gone. It seems that we're on the >> bleeding edge regarding gcc too. > > It was the combination with FORTIFY_SOURCE, I disabled that again for > "debug builds", and pushed it. No errors are thrown any more. We can > enable FORTIFY_SOURCE for debug build too when things have catched up a bit.
It builds without a warning on F19 and not updated F20 now, but still catches this serious bug, which was not detected before the -Og change: http://cgit.freedesktop.org/systemd/systemd/commit/?id=bd4b5df2cb253f130ecdac604e865e3f832c316a Kay _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
