From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com, Jari Aalto <jari.aalto@cante.net>
Subject: Re: RFU: jikes 1.22-2 (Was Re: joe problem on the main list)
Date: Thu, 21 Aug 2008 09:50:00 -0000 [thread overview]
Message-ID: <20080821095104.GH29104@calimero.vinschen.de> (raw)
In-Reply-To: <87sksz7j12.fsf_-_@jondo.cante.net>
On Aug 20 19:23, Jari Aalto wrote:
> "Yaakov (Cygwin Ports)"
> <yselkowitz-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> writes:
> > And what about jikes:
> >
> > http://cygwin.com/ml/cygwin/2006-03/msg00155.html
> > http://cygwin.com/ml/cygwin/2006-05/msg00122.html
> > http://cygwin.com/ml/cygwin/2006-05/msg00133.html
> >
> > I can vouch for the patch, as I've used it to build Ports' classpath.
>
> Patch included, please upload.
>
> Jari
>
> get \
> http://cante.net/~jaalto/tmp/cygwin/jikes/jikes-1.22-2-cygwin.patch \
> http://cante.net/~jaalto/tmp/cygwin/jikes/jikes-1.22-2.sh \
> http://cante.net/~jaalto/tmp/cygwin/jikes/jikes-1.22-2-src.tar.bz2 \
> http://cante.net/~jaalto/tmp/cygwin/jikes/jikes-1.22-2.tar.bz2 \
> http://cante.net/~jaalto/tmp/cygwin/jikes/jikes-1.22.tar.bz2 \
> http://cante.net/~jaalto/tmp/cygwin/jikes/setup.hint
Btw, Jari, what about the joe problem reported on the main Cygwin list
in mid-July?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2008-08-21 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 9:30 joe problem on the main list Corinna Vinschen
2008-07-29 15:42 ` Yaakov (Cygwin Ports)
2008-08-20 16:24 ` RFU: jikes 1.22-2 (Was Re: joe problem on the main list) Jari Aalto
2008-08-20 16:30 ` Corinna Vinschen
2008-08-21 9:50 ` Corinna Vinschen [this message]
2008-08-26 8:20 ` Corinna Vinschen
2008-08-26 20:12 ` RFU: jikes 1.22-2 Jari Aalto
2008-08-27 8:32 ` Corinna Vinschen
2008-08-04 22:57 ` joe problem on the main list Yaakov (Cygwin Ports)
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=20080821095104.GH29104@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
--cc=jari.aalto@cante.net \
/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).