MIME-Version: 1.0
In-Reply-To: <20100626040511.GE28534@ednor.casa.cgf.cx>
References: <4C256292.1060907@users.sourceforge.net>	<20100626040511.GE28534@ednor.casa.cgf.cx>
Date: Sat, 26 Jun 2010 00:15:10 -0400
Message-ID: <AANLkTikWztUTgYZDacWmhg-_YYFFnr1_qyBpk_FXhIgq@mail.gmail.com>
Subject: Re: Cygport improvements
From: NightStrike <nightstrike@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sat, Jun 26, 2010 at 12:05 AM, Christopher Faylor
<cgf-use-the-mailinglist-please@cygwin.com> wrote:
> On Sat, Jun 26, 2010 at 10:14:42AM +0800, JonY wrote:
>>Hello,
>>
>>I am planning to bring mingw-w64 to cygwin. Here are some nits I found
>>when working with it.
>>
>>* It sets CC=3Dgcc
>>While not a major issue, it does present some issues when cross
>>compiling the mingw-w64 CRT.
>
> Why would a Cygwin tool worry about mingw? =A0We've already removed mingw
> support from gcc. =A0Why add it to something called "cygport"?
>
>>* Implicitly setting --prefix=3D/usr
>>While I understand this is suitable for native builds, perhaps adding
>>some cross compile logic to disable this?
>
> Ditto. =A0It's intended to make cygwin packages.
>
> I really don't see how making something mingw aware is a topic for
> the cygwin mailing list.
>
> cgf

He's trying to make a cygwin package that consists of a cross compiler
toolchain for targetting 64-bit windows from a cygwin host.  Cygport
puts some obstacles in the way for doing that.  Maybe you could
suggest how to get around his issues?  That'd be a big help if you
could shed some light on the things he mentioned.

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