gcc build with -O0 results in corrupted -debuginfo package

Reindl Harald h.reindl at thelounge.net
Fri Apr 25 15:48:41 UTC 2014


Am 25.04.2014 17:10, schrieb Adam Jackson:
> On Fri, 2014-04-25 at 16:50 +0200, Reindl Harald wrote:
> 
>> but it don't justify incompatible flags
>> IMHO you enter the area of "undefined behavior" with that
> 
> Your humble opinion is misguided, building without _FORTIFY_SOURCE is an
> entirely reasonable thing for an end developer to want to do on their
> machine, and one we should support

sorry, but you misunderstood me

what i said was the combination of -O0 *and* -D_FORTIFY_SOURCE=2
or specifically "$CFLAGS $RPM_OPT_FLAGS -O0"at the same time feels
like undefined behavior because that contains a lot of default
flags including -D_FORTIFY_SOURCE=2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140425/36ecde27/attachment.sig>


More information about the devel mailing list