X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4C8F249D.9050603@users.sourceforge.net>
Date: Tue, 14 Sep 2010 15:30:37 +0800
From: JonY <jon_y AT users DOT sourceforge DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: mingw64-x86_64-gcc-4.5.1-1
References: <announce DOT 4C8EDA61 DOT 8030506 AT users DOT sourceforge DOT net> <AANLkTikW7P9+0Yxxi77vELMK=H-3-wceJdfobBJQB5Y0 AT mail DOT gmail DOT com> <4C8F1CF2 DOT 8000703 AT users DOT sourceforge DOT net> <4C8F2451 DOT 9020906 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <4C8F2451.9020906@cwilson.fastmail.fm>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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

On 9/14/2010 15:29, Charles Wilson wrote:
> 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
>

So, if /usr/x86_64-w64-mingw32 actually exists, it works?

This looks bad, nonetheless.

Maybe we can fix cygwin by only redirecting known directories like, 
/usr/bin and /usr/lib to those in /. It would probably break third party 
apps, so its not entirely good either.

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