GCC 11

[Sveinar Søpler]

Sveinar

On 30.09.2021 12:03, Eric Pouech wrote:
> Le 29/09/2021 à 21:44, Sveinar Søpler a écrit :
>> Well, debuild seem to put the same CFLAGS/LDFLAGS to gcc-mingw-w64 as 
>> it does to gcc, and i guess one of the "debian hardening" options 
>> puts some flags to mingw's LD that does not fly. This does not happen 
>> when you build "manually", so it is quite likely just a build config 
>> thing.
>>
>> Sorry, for this noise, as this is most certainly unrelated to the 
>> original post. I will do some investigations towards debian build 
>> settings, but i do not think it has much to do with the gcc-11 
>> concerns you have i am afraid, although it could be worth 
>> investigating "build system flags vs. manual compile" (atleast i find 
>> it interesting).
>>
>> Again, i am sorry for the noise.
>
> yes, looks more something like that
>
>
> after some more investigations, it's quite clear that most of the 
> warnings comes with gcc 11.1 and even more with gcc 11.2.
>
> so it should be replaced the title (and content) of this thread gcc11 
> by gcc11.2
>
I am not able to reproduce these warnings with GCC-11.1 on Ubuntu 21.04 
when building with debuild locally. Attaching build.log from 64 bit 
build and config.log from configure.

The issues on the OBS buildserver with all the warnings was fixed by 
removing -Wl,-z,relro (a "hardening" set flag) from the buildsettings.

>
> A+
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: logs.tar.xz
Type: application/x-xz
Size: 169808 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20211002/a1001e82/attachment-0001.xz>