All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building ubuntu/gcc-4_2-branch to get GCJ for arm EABI
Date: Sat, 12 Apr 2008 17:58:51 +0200	[thread overview]
Message-ID: <4800DC3B.9080007@gmx.net> (raw)
In-Reply-To: <35a670560804101007m1d787b4ai97927bb42fcbfe5d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

HI Matthijs,

Matthijs van de Water schrieb:
> I know they're not all needed to get a working arm-linux-gnueabi-gcj.
> But I'm not sure if I should mix GCC versions...
> So I changed my preferred version of GCC to '4.2.3-ubuntu' so that one
> will be used in the entire build and started a clean build. I thought
> I was a good idea to keep all gcc things that are built based on the
> same code-base. Is that a wrong assumption? To test I just did a
> "bitbake glibc" which I presume will build enough to know if things
> work.
That is indeed a good idea. GCJ heavily relies on the BC ABI which is
defined for C++. If you use different compilers things may break.

>>  Please report your results.
> The build has just failed on glibc-intermediate with a linking error:
> cannot find -lgcc_eh. I'll look into that now.
> It has finished building the following stuff:
> binutils-cross-2.18-r1
> gcc-cross-4.2.3-ubuntu-r6
> gcc-cross-initial-4.2.3-ubuntu-r6
> glibc-2.6.1-r3
> glibc-intermediate-2.6.1-r3
> linux-libc-headers-2.6.24-r2
Have a look at gcc-4.2.2.inc. As you there are many patches applied
which for e.g. ARM. It is likely that you need to have those for your
GCC recipe, too.

>>  If you get it working please try whether the GCJ patches can be applied
>>  to any of the existing GCC versions within OE. That way all
>>  distributions in OE can make use of it optionally (when they switch to
>>  this GCC).
> That patch will be massive: there are tons of new .java files....
Which perhaps it makes sense then to get everything working from GCJ
4.3.0 onwards. AFAIK this release contains all the ARM GCJ stuff we need
and we can ask Andrew Haley if important GCJ patches have been
introduced after the 4.3.0 release.

GCC 4.3.0 support in OE is still in its infancy and requires some
workarounds. Keep an eye on this list for news about that.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2008-04-12 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 13:50 Building ubuntu/gcc-4_2-branch to get GCJ for arm EABI Matthijs van de Water
2008-04-10 14:33 ` Robert Schuster
2008-04-10 17:07   ` Matthijs van de Water
2008-04-12 15:58     ` Robert Schuster [this message]
2008-04-12 17:13       ` gcc 4.3.0 status, was: " Koen Kooi
2008-04-23  6:41         ` Matthijs van de Water
2008-04-14 16:32       ` Matthijs van de Water
2008-04-15 15:10         ` Matthijs van de Water
2008-04-16  6:04           ` Robert Schuster
2008-04-21 10:37             ` Matthijs van de Water
2008-04-23  7:33               ` Robert Schuster
2008-04-23 11:44                 ` Matthijs van de Water
2008-04-23 12:32                   ` Mark Brown
2008-05-07 15:19                     ` Matthijs van de Water
2008-04-23 11:48                 ` Philip Balister
2008-04-23 12:07                   ` Graeme Gregory

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=4800DC3B.9080007@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.