public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "bero at arklinux dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/25021]  New: Can't compile ant 1.6.5 to machine code
Date: Thu, 24 Nov 2005 16:46:00 -0000	[thread overview]
Message-ID: <bug-25021-5606@http.gcc.gnu.org/bugzilla/> (raw)

Building ant 1.6.5 normally with gcj 4.0.2 works nicely; trying to compile the
resulting jar files into a binary fails:

After ant dist:
cd bin/lib
LINKTO="-L."
for i in *.jar; do
  [ "$i" = "ant-launcher.jar" ] && continue
  gcj -O2 -fPIC -fjni -findirect-dispatch -shared -Wl,-Bsymbolic -o
lib${i/.jar/.so} $i
  LINKTO="$LINKTO -l${i/.jar/}"
done
gcj -O2 -fjni -findirect-dispatch -o antbin
--main=org.apache.tools.ant.launcher.Launcher ant-launcher.jar $LINKTO

results in

/tmp/cc5M7IPD.o: In function `main':
ccy5f8qg.i:(.text+0x20): undefined reference to
`org::apache::tools::ant::launcher::Launcher::class$'
collect2: ld returned 1 exit status

ant-launcher.jar contains the org.apache.tools.ant.launcher.Launcher class as
expected, and can be run perfectly through gij.


-- 
           Summary: Can't compile ant 1.6.5 to machine code
           Product: gcc
           Version: 4.0.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bero at arklinux dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25021


             reply	other threads:[~2005-11-24 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 16:46 bero at arklinux dot org [this message]
2005-11-24 17:20 ` [Bug java/25021] " bero at arklinux dot org
2005-11-29 18:31 ` tromey at gcc dot gnu dot org

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=bug-25021-5606@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).