From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86)
Date: Sun, 10 Nov 2013 05:31:00 -0000 [thread overview]
Message-ID: <527F1A38.6070400@gmail.com> (raw)
In-Reply-To: <527F0CC2.5060506@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
On 11/10/2013 12:34, marco atzeri wrote:
> Il 11/10/2013 4:31 AM, JonY ha scritto:
>>
>> gcc-4.8.x is finally out for 32bit Cygwin. This should fix the python
>> crash issue.
>>
>
> ok,
> but why is pulling python3 as dependency ?
>
> python3 (3.2.3-1)
> Py3K language interpreter
> Required by: gcc-g++, gcc-java
>
Done, removed.
Yaakov, is there a way to tell Cygport about false positives? If not,
feature request! :)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
prev parent reply other threads:[~2013-11-10 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 3:46 JonY
2013-11-10 4:34 ` marco atzeri
2013-11-10 5:25 ` JonY
2013-11-10 5:31 ` JonY [this message]
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=527F1A38.6070400@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).