public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Me Myself and I <stargate7thsymbol@live.co.uk>
To: <nightstrike@gmail.com>, <gcc-help@gcc.gnu.org>, <java@gcc.gnu.org>
Subject: GCJ on mingw32 resignation.
Date: Fri, 16 Mar 2012 08:01:00 -0000	[thread overview]
Message-ID: <BAY147-W17E8A71C9FB50ED71F61D8D05F0@phx.gbl> (raw)
In-Reply-To: <CAF1jjLuMUENojhFfPVuRhOrJifpe6Xef9o72gk5Oimkc3QnM8A@mail.gmail.com>


Unfortunately, I can't get that far.

gcc-core-4.6.2.tar
gcc-java-4.6.2.tar
gc6.8.tar

are the files I have.  Now, Ive been told that I have to compile gcc-core-4.6.2.tar and
have that running successfully first.  This isn't working, due to an error message
which I learn from the email list is due to an error I must be making, which I am not,
and is therefore impossible.  

So I turn to my gcc-java file, which I try to use standalone without the core file.  I find that it has 4 directories.
I have replaced, configured maked installed 2 of those directories with more up to date versions
of their programs, with no problems.  These 2 are boehm-gc and libffi.

However, I find that in ...gcc/java/ there isn't a configure script at all to start from,
and that in .../libjava/ the configure script fails on the first line.

Am I doing the wrong thing here?  Can gcc-java-4.6.2.tar be used to build my gcj, without the gcc-core-4.6.2.tar

file?  If not, can I please just be sent a link or an archive file of someone's successful build of gcj on windows mingw32
(which is not the eclipse version)?

Since I'm reall not succeeding from source code!


On Thu, Mar 15, 2012 at 5:21 PM, Me Myself and I
<stargate7thsymbol@live.co.uk> wrote:
>
> I'm pretty well giving up on compiling GCJ under mingw32, or Windows 7 for that matter.
 
It shouldn't be that hard.  You just have to replace the boehm-gc with
an upstream version.  The one in the GCC tree doesn't work (for
mingw-w64), and it's a giant massive uphill (losing) battle to get
everyone on the same page to update it.
 
I admit I haven't tried it recently, but I did build it once before.


 		 	   		  

      reply	other threads:[~2012-03-16  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  3:21 Me Myself and I
2012-03-16  3:27 ` NightStrike
2012-03-16  8:01   ` Me Myself and I [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=BAY147-W17E8A71C9FB50ED71F61D8D05F0@phx.gbl \
    --to=stargate7thsymbol@live.co.uk \
    --cc=gcc-help@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=nightstrike@gmail.com \
    /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).