Message-ID: <4C935A00.4000600@users.sourceforge.net>
Date: Fri, 17 Sep 2010 20:07:28 +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: On the new mingw64-i686 packages
References: <4C93513B DOT 90908 AT alice DOT it>
In-Reply-To: <4C93513B.90908@alice.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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

On 9/17/2010 19:30, Angelo Graziosi wrote:
> JonY wrote:
>> It should be in /usr/i686-w64-mingw32/sys-root/mingw/bin/libstdc++-6.dll.
>
> Yes, I know this... so, if I have understood, we *need* to add,
> manually, '/usr/i686-w64-mingw32/sys-root/mingw/bin' to PATH. Right?
>

No, its not a good idea IMHO if we want to support mingw.org and 64-bit 
mingw-w64 in parallel. They all have the same dll names. This brings us 
to the next issue...

> Perhaps, you have to create a mingw32-stdc++-6.dll to put in /usr/bin
> (likewise cygstdc++-6.dll) or a postinstall script which does the job
> (see the lapack packages, for example).
>

I made a libtool patch to fixup the dll names sometime ago, but the 
maintainers were not very happy with creating another new prefix.

For now, the best way is to build the program in Cygwin, start a cmd 
prompt with the correct sys-root added to PATH, and run the program from 
there.

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