From: Dhek Bhun Kho <bhun@chello.nl>
To: Rhug <rhug-rhats@sources.redhat.com>
Subject: Re: Problems with the new Xerces
Date: Sun, 12 Jan 2003 12:09:00 -0000 [thread overview]
Message-ID: <1042373404.1650.34.camel@tasslehof.bhun.net> (raw)
In-Reply-To: <1042211487.6397.46.camel@escape>
Hi there,
I put up a Ant static compiled elf binary on sourceforge.
http://prdownloads.sourceforge.net/salvation/ant-glibc2.3.1-linux-2.4.19-ix86-static-0.0.2.tar.bz2?download
(don't mind the project page too much, it's mostly still super
experimental for me). It was compiled on a glibc2.3.1/linux2.4.19
system. I was just wondering if somebody could point out some resources
about how this inflences binary compatibility for other linux systems.
Or is it irrelevant for static binaries? There something odd with the
gcc3.3 snapshot from 2003-01-09, as the Pass1Verifier from
org.apache.bcel.verifier.statics will throw an exception in the compiler
because gnu.gcj.runtime.StringBuffer is read twice. It could be a local
problem, so I won't submit a PR yet.
greets Abhun.
prev parent reply other threads:[~2003-01-12 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 14:35 Gary Benson
2003-01-10 15:09 ` Anthony Green
2003-01-12 12:09 ` 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=1042373404.1650.34.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).