Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

On 12/07/2016 08:04 AM, Igor Gnatenko wrote: Florian, why only %__global_cflags were changed and not %optflags? Many of packages which don't do %configure, use %optflags. %optflags is for both C and C++. The new flags are meaningless for C++ and apparently accepted by the C++ front end

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

On Tue, Dec 6, 2016 at 9:01 AM, Florian Weimer wrote: > On 12/06/2016 08:27 AM, Ralf Corsepius wrote: >> >> On 12/06/2016 04:44 AM, Orion Poplawski wrote: >> >>> I've run into a reasonable number of failures of (custom) configure >>> checks due to this. Mainly calling exit()

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

On 12/06/2016 08:27 AM, Ralf Corsepius wrote: On 12/06/2016 04:44 AM, Orion Poplawski wrote: I've run into a reasonable number of failures of (custom) configure checks due to this. Mainly calling exit() without including stdlib.h. So keep alert everyone. Unfortunately this can lead to

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

On 12/06/2016 04:44 AM, Orion Poplawski wrote: I've run into a reasonable number of failures of (custom) configure checks due to this. Mainly calling exit() without including stdlib.h. So keep alert everyone. Unfortunately this can lead to unpredictable and perhaps hard to detect changes.

Re: F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates - warning

On 11/10/2016 03:30 AM, Jan Kurik wrote: = Proposed System Wide Change: Fedora 26 C/C++ Compilation Flags Updates = https://fedoraproject.org/wiki/Changes/Fedora26CFlags Change owner(s): * Florian Weimer This change updates the default C/C++ compilation flags, as determined by the