From: Dhek Bhun Kho <bhun@chello.nl>
To: rhug-rhats@sources.redhat.com
Subject: Re: more bugs
Date: Wed, 18 Dec 2002 17:52:00 -0000 [thread overview]
Message-ID: <1040269985.31103.62.camel@tasslehof.bhun.net> (raw)
In-Reply-To: <1040260780.1981.285.camel@escape>
Hi Anthony,
Op do 19-12-2002, om 02:19 schreef Anthony Green:
> Can I submit a libgcj patch to simply extract org.xml and org.w3c into
> their own libraries and leave it at that for now?
Good idea. :D By the way, have you tried to get ant working yet? I
posted some list and things. I found out later that you can also make
dependency lists for Makefiles, but gcj fails that on me. So I can't
help you out with that.
Furthermore Ant is severely broken at the moment. Somehow all the
whitespaces get contracted, e.g:
"-d:pserver arg arg arg"
gets interpeted as "-d:pserverargargarg".
I haven't traced this problem yet. Xerces and xalan aren't very useful
without any programs using it.. ;) Do you need any help with anything?
Greets, bhun.
prev parent reply other threads:[~2002-12-19 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 16:41 Tom Tromey
2002-12-18 17:18 ` Anthony Green
2002-12-18 17:23 ` Tom Tromey
2002-12-18 18:28 ` Anthony Green
2002-12-18 17:52 ` Dhek Bhun Kho [this message]
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=1040269985.31103.62.camel@tasslehof.bhun.net \
--to=bhun@chello.nl \
--cc=rhug-rhats@sources.redhat.com \
/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).