X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4C8F2451.9020906@cwilson.fastmail.fm> Date: Tue, 14 Sep 2010 03:29:21 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1 References:

<4C8F1CF2 DOT 8000703 AT users DOT sourceforge DOT net> In-Reply-To: <4C8F1CF2.8000703@users.sourceforge.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 9/14/2010 2:57 AM, JonY wrote: > That is weird. > > Do you have mingw64 binutils installed? Somehow the cygwin binutils was > used. I don't know about Andy, but I sure do -- and I can reproduce his problem. I suspect there is a "bug" in how the cross tool locates the /usr/x86_64-w64-mingw32/bin directory, given the mount structure: /usr/bin = /bin /usr/lib = /lib BUT /usr/x86_64-w64-mingw32 != /x86_64-w64-mingw32 because if I do THIS: mount -o bind /usr/x86_64-w64-mingw32 /x86_64-w64-mingw32 then /bin/x86_64-w64-mingw32-gcc -o foo foo.c works, just as if I had invoked x86_64-w64-mingw32-gcc -o foo foo.c I say this is a "bug" in quotes, because...well, I'm not sure it fits the definition. It's *our* fault we use a wacky mount structure on cygwin... -- Chuck -- 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