DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=HfqM
	RQad1Qm64FpZ1EU2gXGMfn3QS3Xud1WQASeRw2lhTKwbPR8jB+dyaMzpNVW3WdTV
	iYcq/3vLgUAAombAlloXZE7nW8oqxU1L71j9r0UGNNRGUdDjeF7yNmSPcMRI0hxp
	9+cKYh2ukPmhHVlJWJ9MwzCmZHonE3+XZeOb6hk=
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
Subject: Re: Circular dependency with mingw64-x86_64-runtime
To: cygwin AT cygwin DOT com
References: <5ae67c71 DOT 1c69fb81 DOT 568ef DOT 0244 AT mx DOT google DOT com>
From: JonY <10walls AT gmail DOT com>
Message-ID: <9bbe5b31-7959-4b51-6319-efa82686c125@gmail.com>
Date: Tue, 1 May 2018 13:44:45 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5ae67c71.1c69fb81.568ef.0244@mx.google.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VTLnbIPHvFqlGGevfjcW8qQdxtr247ain"

--VTLnbIPHvFqlGGevfjcW8qQdxtr247ain
Content-Type: multipart/mixed; boundary="ZsifMmYv78KHCyUkoqHKNc1RJFzhKaW8W";
 protected-headers="v1"
From: JonY <10walls AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <9bbe5b31-7959-4b51-6319-efa82686c125 AT gmail DOT com>
Subject: Re: Circular dependency with mingw64-x86_64-runtime
References: <5ae67c71 DOT 1c69fb81 DOT 568ef DOT 0244 AT mx DOT google DOT com>
In-Reply-To: <5ae67c71 DOT 1c69fb81 DOT 568ef DOT 0244 AT mx DOT google DOT com>


--ZsifMmYv78KHCyUkoqHKNc1RJFzhKaW8W
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 04/30/2018 02:16 AM, Steven Penny wrote:
> Here are the requirements for "gcc-core":
>=20
> =C2=A0binutils, cygwin-devel, libatomic1, libgomp1, libisl15, libmpc3,
> libquadmath0,
> =C2=A0libssp0, w32api-headers, w32api-runtime, windows-default-manifest
>=20
> and for "w32api-runtime":
>=20
> =C2=A0w32api-headers
>=20
> Here are the requirements for "mingw64-x86_64-gcc-core":
>=20
> =C2=A0libisl13, libmpc3, mingw64-x86_64-binutils, mingw64-x86_64-headers,
> =C2=A0mingw64-x86_64-runtime, mingw64-x86_64-windows-default-manifest,
> =C2=A0mingw64-x86_64-winpthreads
>=20
> and for "mingw64-x86_64-runtime":
>=20
> =C2=A0libisl13, libmpc3, mingw64-x86_64-binutils, mingw64-x86_64-gcc-core,
> =C2=A0mingw64-x86_64-headers, mingw64-x86_64-windows-default-manifest,
> =C2=A0mingw64-x86_64-winpthreads
>=20
> so "mingw64-x86_64-gcc-core" and "mingw64-x86_64-runtime" require each
> other. I
> think that the requirements for "mingw64-x86_64-runtime" should be
> adjusted on
> so that they are similar to "w32api-runtime".

What is the actual problem you are facing?


--ZsifMmYv78KHCyUkoqHKNc1RJFzhKaW8W--

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

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEE5QrdnbBX9Ppk4bbPcTtf4pwUXUUFAlrob1gSHDEwd2FsbHNA
Z21haWwuY29tAAoJEHE7X+KcFF1FHTQP/R0qxZfNHpP0rTsMHGJCjiBVRHnNpK8f
DNMIj65u88L1aMRQ1fxGfxM6MtFPttREBlJ0ktaZwexkCbmxRI34dh8YgIQhb+6S
GEVY5rX9ijupjQcZ0nBP3yBjP4rEZR9JGT/mjtCuxrpboi5vLt5oQnG7UA7Zkl4A
+xS3h4amJWhxqBlfENi8JGhw3NjjUo0sjWaQ0Ma0GDvgbLEuQbyJ3JaCGsDLZ6pm
JFwAfDttbjKkjodc8aU52JDFPYYuZxSH9/qnGbLPcANonM5rBpYmYIQ+uearBFhT
wGl/rtxSgzDZodIBMGah+FaQ7UpnyhcPeAOO4DCDywNDPjkkoQS+HfZjCXMptQjU
1K6KzsKoyZ8wARKv0KOnvySDefCEF5999f4Kdlmp9kUNkVubZA4mwMEVfp0U3S7E
FZR7x3nPMZ3FRU1QX24rkqCnSo44oI4Z9n1jSETcnGtPE6s0XY6wICHjuFE4H/Fw
An7D0XiVpPfwl9ZI+5Q0UHqmqBq4XDS2I08//qJ8feKtRN8B4R68xQuSgOZJ0Me+
6/AyVHxvSgpgqmfrtqKpQeRgn6lm+//KESi6R+MWGfbcq0SxiUYTh9CXmx7zoJ52
V8H3U0nKVRdfNIL1186cNsGAYKSdmsCRXhdtz8Q4EWw9vxwHHmNYoadBT2lieUIZ
lwmvUXIUt1aU
=ZyKd
-----END PGP SIGNATURE-----

--VTLnbIPHvFqlGGevfjcW8qQdxtr247ain--