On Mon, Dec 24, 2012 at 8:58 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-12-23 21:25-0600 Austin English wrote:
On Dec 23, 2012 7:22 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca
wrote:
The subject line pretty much says it all. Running MinGW/gcc under
wineconsole for any
On 2012-12-28 10:44+0100 Frédéric Delanoy wrote:
On Mon, Dec 24, 2012 at 8:58 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-12-23 21:25-0600 Austin English wrote:
On Dec 23, 2012 7:22 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca
wrote:
The subject line pretty much says it all.
On Fri, Dec 28, 2012 at 11:54 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-12-28 10:44+0100 Frédéric Delanoy wrote:
On Mon, Dec 24, 2012 at 8:58 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-12-23 21:25-0600 Austin English wrote:
On Dec 23, 2012 7:22 PM, Alan W.
The subject line pretty much says it all. Running MinGW/gcc under
wineconsole for any simple test programme should demonstrate the issue
for wine-1.5.20 which is not present in wine-1.5.19 and a fairly large
selection of 1.5.x and MinGW versions I have tried over the last year
or so.
I would be
On Dec 23, 2012 7:22 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
The subject line pretty much says it all. Running MinGW/gcc under
wineconsole for any simple test programme should demonstrate the issue
for wine-1.5.20 which is not present in wine-1.5.19 and a fairly large
selection of
On 2012-12-23 21:25-0600 Austin English wrote:
On Dec 23, 2012 7:22 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
The subject line pretty much says it all. Running MinGW/gcc under
wineconsole for any simple test programme should demonstrate the issue
for wine-1.5.20 which is not present