From: Chris Burdess <dog@bluezoo.org>
To: Me Myself and I <stargate7thsymbol@live.co.uk>
Cc: gcc-help@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: GCJ building
Date: Wed, 14 Mar 2012 12:40:00 -0000 [thread overview]
Message-ID: <1331728822.2573.20.camel@ladybug.local> (raw)
In-Reply-To: <CAM1kHc2-MRbFJCo0T_sc1-tYNgA2-8Y6KqZC-nZVhpiDUxVRfw@mail.gmail.com>
On Wed, 2012-03-14 at 09:13 +0000, David Paterson wrote:
> Sorry, but you obviously haven't followed the step-by-step
> instructions. You may think you are, but you appear to be building in
> the wrong directory - there's no sign of a "compiler" directory name
> in the error messages, and the build should not be happening in the
> source tree. This appears to be just a copy and paste of messages
> from previous emails.
>
> We've asked you several times to paste in the commands you're using,
> but you haven't done that. I have no idea what you're doing, but it
> certainly isn't what everyone keeps telling you to do.
Here is a list of instructions that even my cat could follow:
1. Open a MinGW shell.
2. Type: rm -rf /g; mkdir /g
3. Download the following files from
ftp://gcc.gnu.org/pub/gcc/infrastructure/ :
gmp-4.3.2.tar.bz2
mpfr-2.4.2.tar.bz2
mpc-0.8.1.tar.gz
4. Place these files in the g directory you just created. If you just
accepted all the defaults that the MinGW installer supplied, this will
be at C:\MinGW\msys\1.0\g .
5. Download the following files from
ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.6.3/ :
gcc-4.6.3.tar.bz2
gcc-java-4.6.3.tar.bz2
6. Place these files in the g directory you created.
7. Go back to the MinGW shell window.
8. Type the following:
cd /g
tar jxf gmp-4.3.2.tar.bz2
cd gmp-4.3.2
./configure --prefix=/mingw
make && make install
cd /g
tar jxf mpfr-2.4.2.tar.bz2
cd mpfr-2.4.2
./configure --prefix=/mingw
make && make install
cd /g
tar zxf mpc-0.8.1.tar.gz
cd mpc-0.8.1
./configure --prefix=/mingw
make && make install
cd /g
tar jxf gcc-4.6.3.tar.bz2
tar jxf gcc-java-4.6.3.tar.bz2
mkdir build
cd build
../gcc-4.6.3/configure --prefix=/mingw --enable-java
make && make install
If this doesn't work, you sodded something up: either you typed
something wrong, or you did something else not described here. Start
again from step 1. If it still doesn't work, you probably broke your
MinGW installation. Uninstall it and reinstall it using the defaults,
then start again from step 1.
This results in a working gcj on a clean Windows XP SP3 for me.
prev parent reply other threads:[~2012-03-14 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 2:38 GCJ gen-fib information Me Myself and I
[not found] ` <CAM1kHc1PkRUCkgFOpgcNhAXau36uC5E1q9cvHA4ZC5JuV-wFWg@mail.gmail.com>
2012-03-11 23:51 ` GCJ building Me Myself and I
2012-03-12 10:41 ` David Paterson
2012-03-12 21:30 ` Me Myself and I
[not found] ` <4F5E7971.4050408@digium.com>
2012-03-13 3:17 ` Me Myself and I
2012-03-13 12:26 ` David Paterson
2012-03-14 0:13 ` Me Myself and I
2012-03-14 1:44 ` Ian Lance Taylor
[not found] ` <CAH6eHdSbP4q8-y7q5=b2R3Szr0RHfxfP2rRWqYCTRV5FsiDxCA@mail.gmail.com>
2012-03-14 4:34 ` Me Myself and I
2012-03-14 9:14 ` David Paterson
2012-03-14 12:40 ` Chris Burdess [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=1331728822.2573.20.camel@ladybug.local \
--to=dog@bluezoo.org \
--cc=gcc-help@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=stargate7thsymbol@live.co.uk \
/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).