From: Kevin <lists@gnosysllc.com>
To: gentoo-ppc-user@lists.gentoo.org
Subject: [gentoo-ppc-user] IO exception sun.io.MalformedInputException: Bug 86371
Date: Mon, 23 May 2005 06:57:18 -0400 [thread overview]
Message-ID: <4291B70E.4060909@gnosysllc.com> (raw)
Hi List-
Can anyone here comment on this problem? I've asked on the dev and the
ppc-dev lists and gotten no replies for more than a week, but maybe
someone on this list is seeing these problems besides me.
I've been trying for nearly two months now to get java and ant and
related software to build in ppc/linux, and I keep seeing this same
problem. I've filed two bug reports (86371 and 91815) over the past two
months about it now and with new information I've just turned up today,
could probably file a third related to commons-beanutils. Another user
is also seeing 91815, but I seem to be the only one affected by 86371.
Is the configuration on my box broken? Is this a bug? I seem to be the
only one suffering from 86371 but my configuration may be somewhat
unusual too in that I'm using utf8 wherever possible
(my /etc/locales.build is below). Googling for the
sun.io.MalformedInputException turns up many references to utf8.
aphrodite root # cat /etc/locales.build
en_US/ISO-8859-1
en_US.UTF-8/UTF-8
ja_JP.EUC-JP/EUC-JP
ja_JP.UTF-8/UTF-8
ja_JP/EUC-JP
en_HK/ISO-8859-1
en_PH/ISO-8859-1
de_DE/ISO-8859-1
de_DE@euro/ISO-8859-15
es_MX/ISO-8859-1
fa_IR/UTF-8
fr_FR/ISO-8859-1
fr_FR@euro/ISO-8859-15
it_IT/ISO-8859-1
I could really use some expert help on this. It's affecting OOo,
ant-tasks, commons-beanutils, and several others in that I cannot merge
these packages because of this problem.
TIA.
-Kevin
--
gentoo-ppc-user@gentoo.org mailing list
reply other threads:[~2005-05-23 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4291B70E.4060909@gnosysllc.com \
--to=lists@gnosysllc.com \
--cc=gentoo-ppc-user@lists.gentoo.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