From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Me Myself and I <stargate7thsymbol@live.co.uk>
Cc: gcc-help@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: Please, there now has to be someone who can get this working!
Date: Wed, 22 Feb 2012 02:11:00 -0000 [thread overview]
Message-ID: <CAH6eHdSdARzO51z+BLEM=W5+=nVihZOkfVt1btDp=wta+CsCmA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdR1Ly5CUvk6Vpn6noF=bmnorOZa1M+y1fgeE3g+W3Vmmw@mail.gmail.com>
On 22 February 2012 02:08, Jonathan Wakely wrote:
> On 22 February 2012 01:53, Me Myself and I wrote:
>>
>> I have downloaded
>>
>> gcc-core-4.6.2.tar
>> gcc-java-4.6.2.tar
>>
>> I have found that the both contain a directory named
>>
>> gcc-4.6.2 107 Mb
>> gcc-4.6.2 151 Mb
>>
>> What do I name what, and what should I do from here to
>> build the gcc (presumably first), followed by my gcj?
>
> You don't name anything, just unpack them into the same directory and
> follow the instructions at http://rmathew.com/articles/gcj/bldgcj.html
> (and http://gcc.gnu.org/wiki/InstallingGCC for more general
> instructions)
>
> GCJ will be built as part of GCC, you don't build it separately afterwards.
The full process of building GCC is documented at
http://gcc.gnu.org/install/ which you apparently haven't read, despite
spending several days insisting someone must be able to help you,
because downloading the sources is described at
http://gcc.gnu.org/install/download.html and you don't even seem to
have got that far yet. You should really all read those docs first.
next prev parent reply other threads:[~2012-02-22 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 5:32 Me Myself and I
2012-02-21 10:14 ` David Paterson
2012-02-21 10:30 ` GCJ on Linux Me Myself and I
2012-02-21 11:25 ` Jonathan Wakely
2012-02-21 11:27 ` Please, there now has to be someone who can get this working! Jonathan Wakely
2012-02-22 1:54 ` Me Myself and I
2012-02-22 2:08 ` Jonathan Wakely
2012-02-22 2:11 ` Jonathan Wakely [this message]
2012-02-22 3:02 ` Me Myself and I
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='CAH6eHdSdARzO51z+BLEM=W5+=nVihZOkfVt1btDp=wta+CsCmA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--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).