|
From: | Gregory Smith |
Subject: | Re: [Mingw-cross-env-list] Release 2.19 |
Date: | Wed, 16 Mar 2011 15:28:27 -0400 (EDT) |
User-agent: | Alpine 2.02 (LFD 1266 2009-07-14) |
On Thu, 17 Mar 2011, Tony Theodore wrote:
True, the alternative would probably be a tricky sed replacement or patching autotools... I've checked it in: http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/6b3afa22962a As an aside, these are silent failures when wine is working correctly - if you actually use it for anything, you may want to investigate/re-install. I vaguely recall an issue with binutils assembler on Fedora just before our previous release - it was generating similar "odd" output. You could upgrade to the latest release of binutils and rebuild wine with that to see what happens.
I don't actually use wine on that machine any more, having downgraded the CPU--it's little more than a fileserver. I have left it installed because it seems to expose issues with mingw-cross-env that Fedora users with wine installed may run into. I use the system RPM, I don't compile wine myself.
The machine is also not fully patched, I see wine is a couple versions out of date. I'll upgrade everything before reporting any other issues.
Gregory
[Prev in Thread] | Current Thread | [Next in Thread] |