From: Mark Wielaard <mark@klomp.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: Andrew Haley <aph@redhat.com>,
classpath-patches@gnu.org, java-patches@gcc.gnu.org
Subject: Re: [cp-patches] Fix libjava bootstrap failure around IUCLC
Date: Mon, 26 Mar 2012 11:03:00 -0000 [thread overview]
Message-ID: <1332759797.2848.34.camel@springer.wildebeest.org> (raw)
In-Reply-To: <CAOJsxLHc6kUHuzSq_HdbrY76YQy-bGTNLJOzV6dnZtcPX-4v_A@mail.gmail.com>
On Mon, 2012-03-26 at 13:53 +0300, Pekka Enberg wrote:
> On Mon, Mar 26, 2012 at 1:50 PM, Andrew Haley <aph@redhat.com> wrote:
> >> Btw, why are people not fixing GNU Classpath upstream-first?
> >
> > Because, I guess, no-one is using it. At least, if they were, this
> > bug would have been noticed.
>
> Right. I'm developing and testing with Fedora and Ubuntu on x86 and I
> verify GNU Classpath bootstrap on Darwin at times. I guess Buildbot
> would help here.
It is there on GNU/Linux, OpenBSD and Solaris at least, but there might
be termios out there (apparently freebsd at least) that don't have
IUCLC.
Buildbot is on the TODO list :) Of course even with that we need slaves
for some of the more obscure platforms.
Cheers,
Mark
next prev parent reply other threads:[~2012-03-26 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 16:09 Gerald Pfeifer
2012-03-26 9:01 ` Andrew Haley
2012-03-26 10:11 ` Mark Wielaard
2012-03-26 10:47 ` [cp-patches] " Pekka Enberg
2012-03-26 10:49 ` Andrew Haley
2012-03-26 10:50 ` Andrew Haley
2012-03-26 10:53 ` Pekka Enberg
2012-03-26 11:03 ` Mark Wielaard [this message]
2012-03-26 10:54 ` Mark Wielaard
2012-03-26 10:49 ` Andrew Haley
2012-03-28 19:48 ` Gerald Pfeifer
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=1332759797.2848.34.camel@springer.wildebeest.org \
--to=mark@klomp.org \
--cc=aph@redhat.com \
--cc=classpath-patches@gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=penberg@kernel.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).