From: JonY <10walls@gmail.com>
To: Corinna Vinschen <corinna@vinschen.de>,
cygwin@sourceware.org, yselkowitz@aol.com, glitchmr@myopera.com,
kbrown@cornell.edu, drstacey@tiscali.co.uk, daveroth@acm.org,
me.cygwinstage@cgf.cx, ir0nh34d@gmail.com, Stromeko@NexGo.DE,
yselkowitz@sourceware.org, corinna@sourceware.org,
cgf@sourceware.org
Subject: Re: upset messages
Date: Sun, 10 Nov 2013 02:56:00 -0000 [thread overview]
Message-ID: <527EF5D7.7040904@gmail.com> (raw)
In-Reply-To: <20131109165134.GL16306@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On 11/10/2013 00:51, Corinna Vinschen wrote:
> On Nov 9 21:20, JonY wrote:
>> On 11/9/2013 18:45, Corinna Vinschen wrote:
>>> On Nov 9 10:36, <annoying raw email address> wrote:
>>>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires nonexistent package java-ecj
>>>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires package java-ecj which has no "curr" binary
>>>
>>> I silenced this message for now by removing the nonexisting java-ecj from
>>> gcc/gcc-java/setup.hint, but this looks wrong.
>>>
>>
>> Thanks, already asked Yaakov to put up gcc-ecj, since he already has it
>> in Cygwin ports.
>
> Guess you mean java-ecj...
>
Yes, java-ecj, sorry.
>> What about the odd gcc4 warning?
>
> Should be fixed. I removed gcc4/libstdc++-devel.
>
Thanks.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
next prev parent reply other threads:[~2013-11-10 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131109103606.25923.qmail@sourceware.org>
2013-11-09 10:45 ` Corinna Vinschen
2013-11-09 13:21 ` JonY
2013-11-09 16:51 ` Corinna Vinschen
2013-11-10 2:56 ` JonY [this message]
2013-11-10 19:23 ` Christopher Faylor
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=527EF5D7.7040904@gmail.com \
--to=10walls@gmail.com \
--cc=Stromeko@NexGo.DE \
--cc=cgf@sourceware.org \
--cc=corinna@sourceware.org \
--cc=corinna@vinschen.de \
--cc=cygwin@sourceware.org \
--cc=daveroth@acm.org \
--cc=drstacey@tiscali.co.uk \
--cc=glitchmr@myopera.com \
--cc=ir0nh34d@gmail.com \
--cc=kbrown@cornell.edu \
--cc=me.cygwinstage@cgf.cx \
--cc=yselkowitz@aol.com \
--cc=yselkowitz@sourceware.org \
/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).