[arch-general] [arch-dev-public] Changing compilation flags

Jordan Glover Golden_Miller83 at protonmail.ch
Fri Jul 7 16:17:27 UTC 2017

I'm surprised as it seemed to me that Daniel took it for granted that patch like that will get accepted. Anyway it's hard for an outsider to successfully submit anything to big upstream project. I hope you'll be more lucky if/when you decide to upstream your pie/ssp patches.
It would be nice if makepkg have some conditionals i.e. :
if cc=clang then
cflags="-march=x86-64 -mtune=generic -O2 -pipe -fsanitize=safe-stack -fsanitize=cfi -fvisibility=hidden
if cc=gcc then
cflags="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fstack-check

> -------- Original Message --------
> Subject: Re: [arch-dev-public] Changing compilation flags
> From: evangelos at foutrelis.com
> To: Jordan Glover <Golden_Miller83 at protonmail.ch>
> arch-general at archlinux.org <arch-general at archlinux.org>, Daniel Micay <danielmicay at gmail.com>, Public mailing list for Arch Linux development <arch-dev-public at archlinux.org>, joerg at netbsd.org
> Thanks for trying to push the change upstream. I"m sorry they weren"t
> very receptive of it; your responses were on point and further
> clarified our intended use case.
> I"m not sure what Joerg meant by saying "Arch Linux can"t do
> compiler-specific flag definitions". He could be thinking of a regular
> project that can check for supported compiler flags, but AFAIK that
> concept is not readily transferable to distro-wide flags. (Even if it
> was, it would also apply to stack-check and friends so it"s a weak
> argument in my opinion.)
> At the end of the day, it"s not an issue to carry this patch
> downstream in Arch. :-)

More information about the arch-general mailing list