Have there been any problems with Wine on GCC 4.7?

Austin English austinenglish at gmail.com
Mon Aug 20 23:39:26 CDT 2012


On Mon, Aug 13, 2012 at 4:46 PM, Scott Ritchie <scott at open-vote.org> wrote:
> On 8/13/12 12:55 PM, Eric Pouech wrote:
>>
>>
>>> diff --git a/configure.ac b/configure.ac
>>> index 4bd43d1..c80fd8a 100644
>>> --- a/configure.ac
>>> +++ b/configure.ac
>>> @@ -1746,6 +1746,8 @@ then
>>> WINE_TRY_CFLAGS([-Wtype-limits])
>>> WINE_TRY_CFLAGS([-Wunused-but-set-parameter])
>>> WINE_TRY_CFLAGS([-Wwrite-strings])
>>> + WINE_TRY_CFLAGS([-gdwarf-2])
>>> + WINE_TRY_CFLAGS([-gstrict-dwarf])
>>>
>>> dnl gcc-4.6+ omits frame pointers by default, breaking some copy
>>> protections
>>> case $host_cpu in
>>>
>>> would be simpler, unless I'm missing something.
>>>
>> would work too (even if this would be preferable)
>>
>> + WINE_TRY_CFLAGS([-gdwarf-2 -gstrict-dwarf])
>>
>
> Or I could not patch Wine itself and instead patch it's build instructions
> in the package rules file.
>
> But if Wine indeed doesn't work with GCC's new default settings then it
> should probably be a Wine page (for every distro)

http://source.winehq.org/git/wine.git/commitdiff/3f1dbaf3df0ae8ec2f0e86191eae3879fc422e2d

-- 
-Austin



More information about the wine-devel mailing list