From: Per Bothner <per@bothner.com>
To: rhug-rhats@sources.redhat.com
Subject: rhug libtool problem
Date: Thu, 18 Oct 2001 14:39:00 -0000 [thread overview]
Message-ID: <200110182134.f9ILYgJ07799@eureka.bothner.com> (raw)
I'm confused how people are able to compile rhug without getting these
kinds of errors:
make[2]: Entering directory `/home/bothner/Java/rhug/pgsql-jdbc'
source='upstream/org/postgresql/Field.java' object='upstream/org/postgresql/Field.lo' libtool=yes \
depfile='.deps/upstream/org/postgresql/Field.Plo' tmpdepfile='.deps/upstream/org/postgresql/Field.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile gcj --encoding=UTF-8 -fassume-compiled -fCLASSPATH=upstream -O2 -c -o upstream/org/postgresql/Field.lo `test -f upstream/org/postgresql/Field.java || echo './'`upstream/org/postgresql/Field.java
rm -f upstream/org/postgresql/.libs/Field.lo
gcj --encoding=UTF-8 -fassume-compiled -fCLASSPATH=upstream -O2 -c upstream/org/postgresql/Field.java -MT upstream/org/postgresql/Field.lo -MD -MP -MF .deps/upstream/org/postgresql/Field.TPlo -fPIC -DPIC -o upstream/org/postgresql/Field.ogcj: can't specify `-D' without `--main'
The fix presumably is to require the "multi-language" libtool,
and add --tag=GCJ to LTGCJCOMPILE in the various Makefiles.
My confusion is that people seem to be managing without it. Are
they just building statically?
--Per Bothner
per@bothner.com http://www.bothner.com/per/
next reply other threads:[~2001-10-18 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 14:39 Per Bothner [this message]
2001-10-18 15:50 ` Tom Tromey
2001-10-18 16:18 ` Anthony Green
2001-10-18 16:46 ` Per Bothner
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=200110182134.f9ILYgJ07799@eureka.bothner.com \
--to=per@bothner.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).