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 10:54:00 -0000 [thread overview]
Message-ID: <1332759272.2848.32.camel@springer.wildebeest.org> (raw)
In-Reply-To: <CAOJsxLELbSuvon+izYLwETAssjD55awb=seLCjuVeAFqu3hKog@mail.gmail.com>
On Mon, 2012-03-26 at 13:47 +0300, Pekka Enberg wrote:
> On Mon, Mar 26, 2012 at 1:11 PM, Mark Wielaard <mark@klomp.org> wrote:
> > On Mon, 2012-03-26 at 10:01 +0100, Andrew Haley wrote:
> >> On 03/25/2012 05:08 PM, Gerald Pfeifer wrote:
> >> > 2012-03-25 Gerald Pfeifer <gerald@pfeifer.com>
> >> >
> >> > PR libgcj/52694
> >> > * java/io/natVMConsole.cc (IUCLC): Define, if undefined.
> >>
> >> Sure. WTF is IUCLC anyway? :-)
> >
> > (map) Input (characters) UpperCase (to) Lower Case.
> > It is a non-posix termios extension.
> >
> > patch should also go into upstream classpath.
>
> Yes, please.
>
> Btw, why are people not fixing GNU Classpath upstream-first?
In this case, because libgcj doesn't use the JNI interface for some of
its native implementations. So this was found in the CNI .cc variant.
The patch should be similar though for the jni .c variant.
Cheers,
Mark
next prev parent reply other threads:[~2012-03-26 10:54 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
2012-03-26 10:54 ` Mark Wielaard [this message]
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=1332759272.2848.32.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).