DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=old
	GJ4PgS/fncW6sQ+hj9V8e1oV2aWNM/zP2/J6o0D1nBXMdbnIV9GixJHSJj5Woc9v
	xzu+kUH4A5/SYuRFVWTM08X71Uc96Q516h6LPx/7foXq/bDvQbK8cPgIp9QAPZtK
	ZiOVM8hPyjUYhL4ZGn8hXNTWh9GjoZs+mN/Il074=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <52D05B8F.6090705@junovagen.se>
Date: Fri, 10 Jan 2014 21:43:59 +0100
From: Thomas Nilsson <thomas AT junovagen DOT se>
User-Agent: Postbox 3.0.8 (Windows/20130427)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: /bin before /usr/bin makes i686-w64-mingw-gcc fail
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

During some unfortunate events I happened to get /bin as the first 
directory in my PATH. This caused the gcc cross compilers to fail with:

     i686-w64-mingw32-gcc: error: spawn: No such file or directory

With -v is said

     Using built-in specs.
     COLLECT_GCC=i686-w64-mingw32-gcc
     Target: i686-w64-mingw32
     Configured with: ...  --enable-lto
     Thread model: win32
     gcc version 4.8.2 (GCC)
     COLLECT_GCC_OPTIONS='-v' '-mtune=generic' '-march=pentiumpro'
         cc1 -quiet -v -iprefix /bin/../lib/gcc/i686-w64-mingw32/4.8.2/ 
-U_REENTRANT exe.c -quiet -dumpbase exe.c -mtune=generic 
-march=pentiumpro -auxbase exe -version -o /tmp/cct8mpeq.s
     i686-w64-mingw32-gcc: error: spawn: No such file or directory

As you can see the 'cc1' does not have a path in front of it. After some 
investigation I also found that it did not announce its use of 
COLLECT_LTO_WRAPPER although it was configured with it.

I am just curious if this is expected behvaiour, something I should 
report, or just leave it.

Once I found it, it was not a problem, of course.

Regards,
     Thomas

--
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