DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=Jplqop0PBj5MTalXEUdN/GmwnOK+l
	OKWiDY2JVetdSS5QCKMIqMNPyqCtLV2n1SIU4yfi8JLRuRmgzMmQ55NvOYTTm3/t
	la6xztR0PvoG4XEy6FwFaa0OnFiKkG6z//cMu3frJsy7KeEm8WWhvMCeLiK2aIpv
	yIxXu/d0zPBhwY=
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
Message-ID: <5ae8f950.1c69fb81.5f000.63ab@mx.google.com>
Date: Tue, 01 May 2018 16:33:36 -0700 (PDT)
From: Steven Penny <svnpenn AT gmail DOT com>
Subject: Re: Circular dependency with mingw64-x86_64-runtime
To: cygwin AT cygwin DOT com
References: <9bbe5b31-7959-4b51-6319-efa82686c125 AT gmail DOT com>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.4.0 (github.com/svnpenn/tryst)

On Tue, 1 May 2018 13:44:45, JonY wrote:
> What is the actual problem you are facing?

i already described it: when 2 things depend on each other in this way, that is
an error:

http://wikipedia.org/wiki/Circular_dependency

while setup.exe may account for this, it doesnt change the fact that this is not
correct. ideally one should depend on the other, and *not* vice versa. in this
case "gcc" should depend on "runtime", and not the other way around. the fix is
pretty simple; with "mingw64-x86_64-runtime.cygport", change:

    REQUIRES="mingw64-x86_64-headers mingw64-x86_64-gcc-core"

to

    REQUIRES="mingw64-x86_64-headers"

compare this to "w32api-runtime.cygport":

    REQUIRES="w32api-headers"


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