public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Josh Marinacci <joshua@marinacci.org>
Cc: java@gcc.gnu.org
Subject: Re: Advice on compiling GCJ for ARM
Date: Wed, 22 Sep 2010 08:09:00 -0000	[thread overview]
Message-ID: <4C99B9A8.5080008@redhat.com> (raw)
In-Reply-To: <EE203B3B-9473-4A12-9966-D43203148D97@marinacci.org>

On 21/09/10 15:18, Josh Marinacci wrote:
> 
> On Sep 21, 2010, at 4:55 AM, Andrew Haley wrote:
> 
>> On 21/09/10 04:14, Josh Marinacci wrote:
>>
>>> I've been trying off and on for a week to build a GCJ compiler for
>>> webOS, a Linux variant on ARM, with very little success.  On the
>>> bright side I've started to learn more about how the GCC build
>>> system works. :) My host machine is Mac OSX 10.6.4, Snow
>>> Leopard. I've been able to get GCJ for Mac OSX (darwin) working
>>> (though with a few issues), but I can't the cross compiler to even
>>> finish compiling.
>>
>> Works for me.  You have to build with the right options.  My setup is
>>
>>  $ /home/aph/gcc/gcc-4_5-branch/configure --prefix=/home/aph/x-arm/install --target=arm-linux-gnueabi --with-sysroot=/home/aph/x-arm/rootfs-f12/ --with-headers=/home/aph/x-arm/chroot-arm/usr/include/ -disable-libssp --disable-libgomp --disable-libmudflap --disable-multilib --disable-static --disable-sjlj-exceptions --enable-languages=java
> 
> what version of gcc

4.5 branch: more or less 4.5.1.

> & glibc are you using?

Hmmm, dunno.  Whatever is in Fedora 12: glibc-2.11.2-1.

Andrew.

  reply	other threads:[~2010-09-22  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  3:17 Josh Marinacci
2010-09-21  8:55 ` Andrew Haley
2010-09-21 14:18   ` Josh Marinacci
2010-09-22  8:09     ` Andrew Haley [this message]
2010-09-22 15:05       ` Josh Marinacci
2010-09-23 12:02         ` Andrew Haley
2010-09-22 18:51       ` Dr Andrew John Hughes

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=4C99B9A8.5080008@redhat.com \
    --to=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=joshua@marinacci.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).