From: Andrew Haley <aph@redhat.com>
To: David Michel <dmichel76@googlemail.com>
Cc: java@gcc.gnu.org
Subject: Re: ant with gcc
Date: Mon, 10 Aug 2009 08:57:00 -0000 [thread overview]
Message-ID: <4A7FE0DD.4090204@redhat.com> (raw)
In-Reply-To: <b5bf7a380908070558n2e23f72xe17c4dbea818a18f@mail.gmail.com>
David Michel wrote:
> I have an issue with using ant with gcc:
>
> While with Sun, I can simply set JAVA_HOME as such: export
> JAVA_HOME=/usr/lib/jvm/java-6-sun-1.6.0.14/
> so that ant can find /usr/lib/jvm/java-6-sun-1.6.0.14/lib/tools.jar
> (which is essentially $JAVA_HOME/lib/tools.jar)
>
> Somehow, I have trouble to do the same with my install of gcc:
>
> 'locate tools.jar' returns
> '/local/gcc-4_4-branch/install/lib/jvm/lib/tools.jar' so that I've
> put: export JAVA_HOME=/local/gcc-4_4-branch/install/lib/jvm/
>
> But then, I get this:
>
> $ ant
> Unable to locate tools.jar. Expected to find it in
> /local/gcc-4_4-branch/install/lib/tools.jar
> Buildfile: build.xml does not exist!
> Build failed
>
> Any clues ?
Ant makes some assumptions about the layout of an installed Java runtime.
There are two ways you can solve this problem with gcj.
1. If you are building and installing gcc from source, it can
create a JAVA_HOME directory:
`--enable-java-home'
If enabled, this creates a JPackage compatible SDK environment
during install. Note that if -enable-java-home is used,
-with-arch-directory=ARCH must also be specified.
`--with-arch-directory=ARCH'
Specifies the name to use for the `jre/lib/ARCH' directory in the
SDK environment created when -enable-java-home is passed. Typical
names for this directory include i386, amd64, ia64, etc.
2. If you are running on a GNU/Linux distro like Fedora, install
the java-1.5.0-gcj package or its equivalent.
Andrew.
prev parent reply other threads:[~2009-08-10 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:59 David Michel
2009-08-10 8:57 ` Andrew Haley [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=4A7FE0DD.4090204@redhat.com \
--to=aph@redhat.com \
--cc=dmichel76@googlemail.com \
--cc=java@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).