From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Circular dependency with mingw64-x86_64-runtime
Date: Tue, 01 May 2018 13:45:00 -0000 [thread overview]
Message-ID: <9bbe5b31-7959-4b51-6319-efa82686c125@gmail.com> (raw)
In-Reply-To: <5ae67c71.1c69fb81.568ef.0244@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
On 04/30/2018 02:16 AM, Steven Penny wrote:
> Here are the requirements for "gcc-core":
>
> binutils, cygwin-devel, libatomic1, libgomp1, libisl15, libmpc3,
> libquadmath0,
> libssp0, w32api-headers, w32api-runtime, windows-default-manifest
>
> and for "w32api-runtime":
>
> w32api-headers
>
> Here are the requirements for "mingw64-x86_64-gcc-core":
>
> libisl13, libmpc3, mingw64-x86_64-binutils, mingw64-x86_64-headers,
> mingw64-x86_64-runtime, mingw64-x86_64-windows-default-manifest,
> mingw64-x86_64-winpthreads
>
> and for "mingw64-x86_64-runtime":
>
> libisl13, libmpc3, mingw64-x86_64-binutils, mingw64-x86_64-gcc-core,
> mingw64-x86_64-headers, mingw64-x86_64-windows-default-manifest,
> mingw64-x86_64-winpthreads
>
> 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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2018-05-01 13:45 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 [this message]
2018-05-01 23:33 ` Steven Penny
2018-05-02 10:47 ` JonY
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=9bbe5b31-7959-4b51-6319-efa82686c125@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).