X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=s4LAPLEVpj3P/OthCiRllgYHvvA=; b=j7L
	yqbbEDmBKIpFajuWyYyaw1FxEhAkPi7/HNLScYRZ0oOwICqf7iKHN/YNd2AxRpG2
	jfKAnI0747bfiVLaxWAOpRhAmQXr2dyFif5pDZoPeN1cz5szQKRnU+TE6txjIdE0
	WYlG0psvO+0a85pA04kYnJWB17dWb29QG31HFoks=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:751, H*UA:github.com, H*M:1c69fb81, H*M:google
X-HELO:	mail-qt0-f196.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:subject:to:references :user-agent; bh=asGE9BcGponhRJgv6LDYboOrVCJ7Q6rFaRoh0nPGDnU=; b=anQZVTp3+ugr333EWUWHsvqaU0amFII6FOTDtzGcKQncY8Lx4oy2Nsb+k3d7SrbOHR 9N73wuZ8GdU1pHjhwfE8N4iTzU1XgkHBWp9MyxcA5WQLjc8kpGEBO5NEHSkKYpP0KrAq Zmf2he1DxrodnICoGtvzc8OUtac+qetLhr2E1BfK/BDwRuE61iyjgzvmrogCfcZCh16Y LvdmcUNDt59eKtXmr2xnLE6/UF2DrN19X3/DLd8gqtPUXQOcuD3j/71D1AZWkTeE14+C HnAsOnf0tKqH8pmhQRe36HSXaRg652Mv0UpzUBwtsIVm+UgJBK3XSPR5MBMvf9mZ8K5x DxIQ==
X-Gm-Message-State:	ALQs6tAgpCFU1BE/ZljBRp++mdazAWTALL+V7QmdHHLHV+Lf3CQEL8cE 1OjUDgOFrrfQBrV26zZo+DYRhQ==
X-Google-Smtp-Source:	AB8JxZqR6hhXoU58odk6+NVNKW4+wYE9c2193g9YUBpl1u+i9jYqvOCDVfOs4u6DobMNpDj5SGXvsg==
X-Received:	by 2002:a0c:f8c9:: with SMTP id h9-v6mr14866527qvo.122.1525217617227; Tue, 01 May 2018 16:33:37 -0700 (PDT)
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>
X-Google-Original-From:	Steven Penny
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>
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

- Raw text -