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: Wed, 16 Apr 2008 08:04:18 +0200 [thread overview]
Message-ID: <480596E2.7030906@gmx.net> (raw)
In-Reply-To: <35a670560804150810k603d1986t4e02eefa7f411728@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Hi.
Matthijs van de Water schrieb:
> 2) Split out all GCJ related stuff to compile in a separate set of
> tasks so that it does not always get build, because this takes ages
> and loads of memory.
I don't think that is possible atm. GCJ is part of a GCC build and can
only be enabled or disabled at configuration time.
I did a quick glance at the gcc-package-*.inc recipes and they do not
provide packaging info for GCJ specifically. So either things end up
in another binary package or they end up nowhere. I'll have a look at that.
> I'm not sure about the best way to get (2)... any suggestions are welcome.
>
> Regards,
> Matthijs
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-04-16 6:04 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
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 [this message]
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=480596E2.7030906@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.