RE: Troubles using apbuild

> Maybe apbuild should set this flag automatically. What do you think?
> Do you know if that will cause any trouble, Eugene?

Shouldn't cause any trouble. Besides making code more vulnerable to
buffer overruns that fortify tries to prevent. Or rather making it as
vulnerable as it would have been if we built it on older systems.

But if those symbols are missing in older glibc, there is not much we
can do. Anybody knows what's minimum glibc version for fortify symbols? 

I guess one way would be for apgcc to remove any -D_FORTIFY_SOURCE from
cmd line, or add -U_FORTIFY_SOURCE

Also stack protector will introduce new symbols in similar way. There is
-fno-stack-protector-all flag to turn it off, but it isn't implemented
of all gcc versions so unrecognized flag will just fail. apgcc can
remove any appearances of -fstack-protector-all or -fstack-protector
though. I doubt it is ever default.


---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]