From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Circular dependency with mingw64-x86_64-runtime
Date: Wed, 02 May 2018 10:47:00 -0000 [thread overview]
Message-ID: <234104cd-8a77-161d-7d56-4c270403acea@gmail.com> (raw)
In-Reply-To: <5ae8f950.1c69fb81.5f000.63ab@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]
On 05/01/2018 11:33 PM, Steven Penny wrote:
> 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
>
That is not a problem affecting Cygwin.
> 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"
>
Perhaps in the next rebuild.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2018-05-02 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 2:16 Steven Penny
2018-05-01 13:45 ` JonY
2018-05-01 23:33 ` Steven Penny
2018-05-02 10:47 ` JonY [this message]
2018-05-02 13:31 ` Kaz Kylheku
2018-05-03 12:20 ` Andrey Repin
2018-05-02 15:22 ` Mikhail Usenko via cygwin
2018-05-02 15:26 ` Vince Rice
2018-05-02 15:55 ` Mikhail Usenko via cygwin
2018-05-02 16:18 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=234104cd-8a77-161d-7d56-4c270403acea@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).