Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
Thanks, Scott Ritchie
On Mon, Jul 23, 2012 at 7:06 PM, Scott Ritchie scott@open-vote.org wrote:
Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
Thanks, Scott Ritchie
My understanding was that the problems introduced in 4.6 are still in 4.7.
On 07/23/2012 07:44 PM, Austin English wrote:
On Mon, Jul 23, 2012 at 7:06 PM, Scott Ritchie scott@open-vote.org wrote:
Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
Thanks, Scott Ritchie
My understanding was that the problems introduced in 4.6 are still in 4.7.
Would you mind pointing me to the GCC bugs / test cases we have for this? I seem to remember them being a bit impractical (ie, run this 2 gb proprietary app and watch it break), but I think I can help refer the right people.
Thanks, Scott Ritchie
On Mon, Jul 23, 2012 at 07:06:21PM -0700, Scott Ritchie wrote:
Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
For what its worth, openSUSE 12.2 (in RC Phase) has gcc 4.7 and builds with Wine with it, so far I have no bug reports.
Ciao, Marcus
Le 24/07/2012 04:06, Scott Ritchie a écrit :
Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
Thanks, Scott Ritchie
afaik, gcc 4.7 enables by default dwarf4 as its default debug format, whilst wine (dbghelp) only supports dwarf2 it generates a lot of conbursome backtraces in winegdb I've started to add dwarf4 support to wine, but don't hold your breath (it's going to be hard and tedious afaict and will require quite a few changes to dbghelp for correctness) (and I have little time right now <g>)
BTW : fedora 17 ships with gcc 4.7
A+
On 08/12/2012 01:08 AM, Eric Pouech wrote:
Le 24/07/2012 04:06, Scott Ritchie a écrit :
Wine is the last remaining package still depending on GCC 4.5 in the current Ubuntu alpha, it would be nice to drop GCC 4.5 and forward port Wine, however 4.6 is known to not work too well.
But now we have 4.7 -- have there been any bugs attributed to its usage?
Thanks, Scott Ritchie
afaik, gcc 4.7 enables by default dwarf4 as its default debug format, whilst wine (dbghelp) only supports dwarf2 it generates a lot of conbursome backtraces in winegdb I've started to add dwarf4 support to wine, but don't hold your breath (it's going to be hard and tedious afaict and will require quite a few changes to dbghelp for correctness) (and I have little time right now <g>)
BTW : fedora 17 ships with gcc 4.7
A+
In the meantime, I suppose I could enable the -gdwarf-2 compiler option.
Thanks, Scott Ritchie
In the meantime, I suppose I could enable the -gdwarf-2 compiler option.
yes (but it's a bit more tricky than it sounds) something like this will do
A+
diff --git a/configure.ac b/configure.ac index 4bd43d1..2624dc1 100644 --- a/configure.ac +++ b/configure.ac @@ -236,6 +236,12 @@ then AC_SUBST(TARGETFLAGS,"-b $host_alias $TARGETFLAGS") fi
+dnl Check the debug format (force pure dwarf-2 debug format until we correctly support other versions) +tmp_cflags=$CFLAGS +CFLAGS=`echo $CFLAGS | sed -e 's/-g\>/-gdwarf-2 -gstrict-dwarf/'` +AC_LINK_IFELSE([AC_LANG_SOURCE([[int main(int argc, char **argv) { return 0; }]])], + [], [CFLAGS=$tmp_cflags]) + dnl Check for flex AC_CHECK_PROGS(FLEX,flex,none) if test "$FLEX" = "none"
On Mon, Aug 13, 2012 at 2:29 PM, Eric Pouech eric.pouech@orange.fr wrote:
In the meantime, I suppose I could enable the -gdwarf-2 compiler option.
yes (but it's a bit more tricky than it sounds) something like this will do
A+
diff --git a/configure.ac b/configure.ac index 4bd43d1..2624dc1 100644 --- a/configure.ac +++ b/configure.ac @@ -236,6 +236,12 @@ then AC_SUBST(TARGETFLAGS,"-b $host_alias $TARGETFLAGS") fi
+dnl Check the debug format (force pure dwarf-2 debug format until we correctly support other versions) +tmp_cflags=$CFLAGS +CFLAGS=`echo $CFLAGS | sed -e 's/-g\>/-gdwarf-2 -gstrict-dwarf/'` +AC_LINK_IFELSE([AC_LANG_SOURCE([[int main(int argc, char **argv) { return 0; }]])],
[], [CFLAGS=$tmp_cflags])dnl Check for flex AC_CHECK_PROGS(FLEX,flex,none) if test "$FLEX" = "none"
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.
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])
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)
On Mon, Aug 13, 2012 at 4:46 PM, Scott Ritchie scott@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/3f1dbaf3df0ae8ec2f0e86191ea...
http://source.winehq.org/git/wine.git/commitdiff/3f1dbaf3df0ae8ec2f0e86191ea...
-- -Austin
the trouble with this patch is that it enables debug info whatever the default configuration is... A+
On Mon, Aug 20, 2012 at 11:55 PM, Eric Pouech eric.pouech@orange.fr wrote:
http://source.winehq.org/git/wine.git/commitdiff/3f1dbaf3df0ae8ec2f0e86191ea...
-- -Austin
the trouble with this patch is that it enables debug info whatever the default configuration is... A+
-- Eric Pouech
-g was already the default. Most packagers (to my knowledge) provide a separate debug package, which isn't installed by default.
On 8/21/12 12:17 PM, Austin English wrote:
On Mon, Aug 20, 2012 at 11:55 PM, Eric Pouech eric.pouech@orange.fr wrote:
http://source.winehq.org/git/wine.git/commitdiff/3f1dbaf3df0ae8ec2f0e86191ea...
-- -Austin
the trouble with this patch is that it enables debug info whatever the default configuration is... A+
-- Eric Pouech
-g was already the default. Most packagers (to my knowledge) provide a separate debug package, which isn't installed by default.
Correct, the symbols get split out (in Ubuntu Packaging this is handled mostly automatically after just giving the name of the debug package)
-Scott Ritchie
-g was already the default. Most packagers (to my knowledge) provide a separate debug package, which isn't installed by default.
i'm not especially speaking of packagers, but folks who compile wine themselves with something like: ./configure CFLAGS=-O2 and your patch forces -gdwarf2 (whatever -g is requested or not in CFLAGS) hence providing debug info when the user didn't ask for it
A+
On Thu, Aug 23, 2012 at 12:56 PM, Eric Pouech eric.pouech@orange.fr wrote:
-g was already the default. Most packagers (to my knowledge) provide a separate debug package, which isn't installed by default.
i'm not especially speaking of packagers, but folks who compile wine themselves with something like: ./configure CFLAGS=-O2 and your patch forces -gdwarf2 (whatever -g is requested or not in CFLAGS) hence providing debug info when the user didn't ask for it
A+
AJ's taken care of it: http://source.winehq.org/git/wine.git/commitdiff/ce48e2c8ab4537fb57e4416d03f...
-
Austin English -
Eric Pouech -
Marcus Meissner -
Scott Ritchie