X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Wed, 27 Jan 2010 15:10:05 +0100
From: Vincent Richomme <forumer AT smartmobili DOT com>
To: <mingw-dvlpr AT lists DOT sourceforge DOT net>, <cygwin AT cygwin DOT com>
Subject: flashing console
Message-ID: <dd3af8517fbabfc8fb2cb461fc4ab969@mail.smartmobili.com>
X-Sender: forumer AT smartmobili DOT com
User-Agent: RoundCube Webmail/0.2
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Hi,

I am playing regularly with cygwin and mingw(w64) on a Windows 7 64 bits
computer and I have noticed something that 
I already read on cygwin ML about the creation of a new console when there
is a fork.
So here is the story:

I wanted to compile clang on msys/mingw so I have downloaded latest
package + a better console app (console from SF)
and enter the well known sequence : configure make && make install.
Unfortunately I got a memory error due to linker(something like memory
exhausted) so before I give up
I have donwnloaded sources from mingw-w64 project to generate a gcc-4.3.3
toolchain.
With this new toolchain I was able to compile clang.

However console application was buggy because I couldn't copy/paste so
finally I move back to rxvt and
now when trying to compile with default mingw toolchain a package using
autotools I get this flashing console.
BUT wait when I try with the toolchain from mingw-w64 I don't have it.

So to check this I have opened two rxvt consoles and in one of it I have
added mingw-w64 path to default path
while the other use the mingw gcc.

if I enter gcc --version with mingw toolchain I can see that a console is
opened/close and I get
Vincent AT VINCENT-PC ~/tmp/llvm
$ gcc --version
gcc.exe (GCC) 4.4.0

When using mingw-w64(export PATH=/opt/cross_w32/bin:$PATH) no console is
opened
 Vincent AT VINCENT-PC ~/tmp/llvm
$ gcc --version
gcc (GCC) 4.4.3


So sorry to post on both mailing list but is it normal that one version
opens a console while the other doesn't.
Maybe there is something interesting here, what do you think ?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple