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

2017-07-12 Thread Alex Xu via arch-general
spec file? only supported by gcc, but that seems to be kinda the point here. I think this is what most distros do (and possibly also how --enable-default-* works).

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

2017-07-09 Thread Jordan Glover via arch-general
set different CC= option in PKGBUILD or globally in makepkg.conf (it's already possible but flags have to be also manually changed). > Original Message > Subject: Re: [arch-general] [arch-dev-public] Changing compilation flags > From: arch-general@archlinux.org >

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

2017-07-08 Thread Eli Schwartz via arch-general
On 07/08/2017 06:53 AM, LoneVVolf wrote: > On 08-07-17 04:31, Evangelos Foutras via arch-general wrote: >> There are multiple ways the compiler can be selected; two of them are: 1) >> exporting CC/CXX in the PKGBUILD and 2) the project's configure script >> picking one of the available compilers. m

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

2017-07-08 Thread LoneVVolf
On 08-07-17 04:31, Evangelos Foutras via arch-general wrote: There are multiple ways the compiler can be selected; two of them are: 1) exporting CC/CXX in the PKGBUILD and 2) the project's configure script picking one of the available compilers. makepkg can't realistically know which compiler is

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

2017-07-07 Thread Evangelos Foutras via arch-general
On 7 July 2017 at 19:17, Jordan Glover wrote: > 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 t

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

2017-07-07 Thread Jordan Glover via arch-general
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

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

2017-07-07 Thread Evangelos Foutras via arch-general
On 7 July 2017 at 16:39, Jordan Glover wrote: > FYI clang devs don't want to take 1 line patch adding another no-op flag > upstream. > https://lists.llvm.org/pipermail/cfe-dev/2017-July/054588.html Thanks for trying to push the change upstream. I'm sorry they weren't very receptive of it; your re

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

2017-07-07 Thread Jordan Glover via arch-general
FYI clang devs don't want to take 1 line patch adding another no-op flag upstream. https://lists.llvm.org/pipermail/cfe-dev/2017-July/054588.html > Original Message > Subject: Re: [arch-dev-public] Changing compilation flags > From: arch-dev-pub...@archlinux.org > To: Evangelos