public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/19882] fail to create shared lib from jar - 2 instances, xerces and log4
Date: Fri, 11 Feb 2005 16:40:00 -0000	[thread overview]
Message-ID: <20050211052851.6004.qmail@sourceware.org> (raw)
In-Reply-To: <20050210220850.19882.delarosa@ilstechnology.com>


------- Additional Comments From rmathew at gcc dot gnu dot org  2005-02-11 05:28 -------
(In reply to comment #2)
> Sorry for the dumb question. Where do I get the binaries for version 4. I assume
> that you meant gcc 4.0 right ? Any pointer are appreciated.

See:

  http://gcc.gnu.org/cvs.html

for how to get the latest sources from the 
GCC CVS repository.

On a modern Linux system, it's rather easy
to compile GCC from sources. Just be
sure to use a build folder separate from
the source folder. For example, I use the
following configuration command:

$GCC_SRC_DIR/configure --prefix=$HOME/gcc --enable-languages=c,c++,java \
--disable-nls --disable-checking --disable-libmudflap \
--disable-debug --enable-threads=posix --enable-__cxa_atexit

and then "make bootstrap" followed by "make install"
from within the build folder. (You'll have to tweak
the command line above to suit your setup.)

Once you've built and installed this, you 
should see "How to BC compile with GCJ" in the
GCC Wiki:

http://gcc.gnu.org/wiki/How%20to%20BC%20compile%20with%20GCJ

Hope this helps,
Ranjit.

-- 


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


  parent reply	other threads:[~2005-02-11  5:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 23:11 [Bug java/19882] New: " delarosa at ilstechnology dot com
2005-02-10 23:28 ` [Bug java/19882] " mark at klomp dot org
2005-02-11  2:52 ` delarosa at ilstechnology dot com
2005-02-11 16:40 ` rmathew at gcc dot gnu dot org [this message]
2005-02-12 22:31 ` pinskia at gcc dot gnu dot org
2005-08-17  3:21 ` pinskia 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=20050211052851.6004.qmail@sourceware.org \
    --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).