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: Compiling gcc.
Date: Fri, 24 Feb 2012 09:05:00 -0000 [thread overview]
Message-ID: <CAH6eHdR6AquwDJ7+8Kqw30T8sgz189+pfhWcgtg0zjk7XoykOQ@mail.gmail.com> (raw)
In-Reply-To: <BAY147-W593EEF067FBE2CE5D865E8D06A0@phx.gbl>
Again, please don't cross-post to subscription-only lists, it breaks
Reply-to-all.
On 24 February 2012 05:30, Me Myself and I wrote:
>
> I have
>
> gcc-core-4.6.2.tar
>
> Operating under a unix-esque environment. Coincidentally, I have
>
> gcc-java-4.6.2.tar
>
> as subdirectories inside the former, which I am told will compile along with the former
> automatically, with no further input.
You should have unpacked the archives into the same directory, so you
have libjava directory under the top-level gcc-4.6.2 directory. You
do not want two levels of gcc-4.6.2, i.e. gcc-4.6.2/gcc-4.6.2/libjava
> What do I do to get the gcc-core-4.6.2.tar compiled, built and compiling?
Read the links I sent you!
http://gcc.gnu.org/wiki/InstallingGCC for an overview
http://gcc.gnu.org/install/ for the full instructions.
If you're trying to build a cross-compiler for Windows, you already
posted rmathew's instructions, which seem like a good start.
Have you even tried to follow those instructions, or are you just
starting yet another thread with the same questions?
next prev parent reply other threads:[~2012-02-24 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 5:30 Me Myself and I
2012-02-24 9:05 ` Jonathan Wakely [this message]
2012-02-24 10:42 ` Bryce McKinlay
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=CAH6eHdR6AquwDJ7+8Kqw30T8sgz189+pfhWcgtg0zjk7XoykOQ@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).