From: Anthony Green <green@redhat.com>
To: Nicholas Wourms <nwourms@myrealbox.com>
Cc: rhug-rhats@sources.redhat.com, aoliva@redhat.co
Subject: Re: [jakarta-servletapi]: libtool problems
Date: Mon, 02 Sep 2002 06:44:00 -0000 [thread overview]
Message-ID: <1030974256.8068.24.camel@dhcppc2> (raw)
In-Reply-To: <3D7365B2.7070704@myrealbox.com>
On Mon, 2002-09-02 at 06:20, Nicholas Wourms wrote:
> Ok, I guess I should fess up to the fact that I'm trying to build it on
> your sister project, Cygwin. I take it, then, that the problem lies in
> libtool?
Not necessarily. gcj builds object files out of property files with
the --resource flag. libtool doesn't know how to do this, so I haven't
been using the regular libtool build mechanisms. This makes libtool
complain that it's linking libtool and non-libtool object files together
-- but like I said, it's just a warning under Linux. I've CC'd Alex
Oliva in case he has any ideas. Teaching libtool about gcj resource
files will probably be hard. Perhaps we could fake it out by generating
.lo files on our own...
AG
prev parent reply other threads:[~2002-09-02 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 20:36 Nicholas Wourms
2002-09-02 6:00 ` Anthony Green
2002-09-02 6:21 ` Nicholas Wourms
2002-09-02 6:44 ` Anthony Green [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=1030974256.8068.24.camel@dhcppc2 \
--to=green@redhat.com \
--cc=aoliva@redhat.co \
--cc=nwourms@myrealbox.com \
--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).