From: Stefan Seefeld <seefeld@sympatico.ca>
To: rhug-rhats@sources.redhat.com
Subject: Re: [tromey@redhat.com (Tom Tromey)] FAIL: rhug build on Sat May 3 03:26:43 MDT 2003
Date: Wed, 21 May 2003 13:01:00 -0000 [thread overview]
Message-ID: <b0612bfc8c9c93b3000efa9a2d4d98d13ecb7b11@Orthosoft.ca> (raw)
In-Reply-To: <1053502285.3465.9.camel@escape>
Anthony Green wrote:
> On Sat, 2003-05-03 at 15:08, Tom Tromey wrote:
>
>>rhug hasn't built for me in quite a while.
>>However, this is a different failure than usual.
>
>
> I was able to build gnu.readline without incident.
>
> My build falls down in xerces...
>
> libtool: link:
> `upstream/src/org/apache/xerces/impl/msg/DOMMessages.properties.lo' is
> not a valid libtool object
just for the record, I was able to build almost all of rhug with gcc
3.3, with only slight changes to the Makefiles (adding some --classpath
arguments to gcjh...).
I occasionally run 'make clear', and then I observed the same, i.e. lots
of references to *.lo files from within .la files, which couldn't be
resolved/built/whatever.
Running 'make install' revealed another error, again in the libtool
department: libtool tries to install archives (.a files), while none
are built.
Anyways, with a little bit of manual fine-tuning I was able to run ant,
which is much further than I ever got.
Thanks !
Stefan
prev parent reply other threads:[~2003-05-21 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 22:16 Tom Tromey
2003-05-06 13:24 ` Anthony Green
2003-05-21 7:31 ` Anthony Green
2003-05-21 9:38 ` Gary Benson
2003-05-21 15:46 ` Anthony Green
2003-05-21 16:44 ` Gary Benson
2003-05-21 19:15 ` Anthony Green
[not found] ` <20030522092501.GB15469@redhat.com>
[not found] ` <1053620895.3465.797.camel@escape>
2003-05-22 16:44 ` Gary Benson
2003-05-22 18:48 ` Anthony Green
2003-05-23 8:42 ` Gary Benson
2003-05-21 13:01 ` Stefan Seefeld [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=b0612bfc8c9c93b3000efa9a2d4d98d13ecb7b11@Orthosoft.ca \
--to=seefeld@sympatico.ca \
--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).