public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Me Myself and I <stargate7thsymbol@live.co.uk>
To: <gcc-help@gcc.gnu.org>, <java@gcc.gnu.org>
Subject: GCJ confusion.
Date: Sat, 17 Mar 2012 01:32:00 -0000	[thread overview]
Message-ID: <BAY147-W10C1307CC9DD7C5D7B622AD05C0@phx.gbl> (raw)


Unfortunately, I can't get that far.
 
gcc-core-4.6.2.tar
gcc-java-4.6.2.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.  Unfortunately, I can't figure out how to get past this.

I have turned to the Java Native Compiler.  I have tried the Eclipse GCJ, which while functional,
compiles far to much into my executable file for my needs. I have tried gcc-full-4.4.0-mingw32-bin-2.tar,
which while compiling my source code, doesn't seem to support java 1.5 related syntax and library needs,
so my programs are killed and quit early.
 
So is it possible for someone to just give me the file or a link to the latest built GCJ, so I can run it
in Windows/mingw32/mingw64 ?

And if they have had success in building that file themselves, to send along some basics as to what they have done with
that file?


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-17  1:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-W10C1307CC9DD7C5D7B622AD05C0@phx.gbl \
    --to=stargate7thsymbol@live.co.uk \
    --cc=gcc-help@gcc.gnu.org \
    --cc=java@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).