X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-8.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_PGP_SIGNED,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
Message-ID:	<503DC812.5060704@users.sourceforge.net>
Date:	Wed, 29 Aug 2012 15:43:14 +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: mingw32-gcc and posix paths
References:	<1346220462071-92376 DOT post AT n5 DOT nabble DOT com> <1346220956451-92378 DOT post AT n5 DOT nabble DOT com>
In-Reply-To:	<1346220956451-92378.post@n5.nabble.com>
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

--------------enig47CF8918230BAD6846ABEC8A
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 8/29/2012 14:15, thoni56 wrote:
>=20
> thoni56 wrote
>>
>> I'm in the process of going from gcc3 to gcc4. For one project I need to
>> build both cygwin and win32 executables so "-mno-cygwin" to "mingw32-gcc"
>> was an initial hurdle.
>>
>> However that is now sorted out, but one thing puzzles me. If the mingw32
>> is a cygwin cross-compiler why does it not accept paths in the host form=
at
>> (meaning cygwin, posix)? To me this seems very natural. Maybe  I'm biase=
d,
>> but I see no other tools do that, expecting the command line to have the
>> format of the *target*.
>>
>> mingw32-gcc also produces .d files in its native format by the way.
>>
>=20
> I forgot to add that it is really this .d thing that makes it problematic.
> The makefiles generate separate subdirectories for various targets and al=
so
> sets CFLAGS, CC, LINK et al. differently to allow different settings (and
> compilers, was my theory) for the different targets.
>=20
> Since mingw32-gcc and gcc generates .d files in incompatible formats (gcc
> really doesn't like "c:\..." in its .d files...) and those are included in
> the make file, even using different make:s does not solve the problem for
> me.
>=20
> Any ideas?

Cygwin does not and never has provided a "mingw32-gcc", but it has a
"i686-pc-mingw32-gcc", it is likely you used those from mingw.org.

mingw.org provides native toolchains, so it is not Cygwin aware, it
would explain your path issues.



--------------enig47CF8918230BAD6846ABEC8A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iEYEARECAAYFAlA9yBcACgkQp56AKe10wHc/bQCfWIq9U9H6IBCK1ODV5kLhrNZ4
VkQAn1TmnsvXqEa8jqum8RAH32zTQ52V
=1vRo
-----END PGP SIGNATURE-----

--------------enig47CF8918230BAD6846ABEC8A--

- Raw text -