From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: merging recipes from Jalimo
Date: Wed, 19 Dec 2007 14:54:57 +0100 [thread overview]
Message-ID: <476922B1.4090102@gmx.net> (raw)
In-Reply-To: <475EDA2B.8080109@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hi,
thanks for all the information. Contrary to what I said in other posts I
will look in providing a completely self-hosting java toolchain. This
will include building one additional instance of classpath and cacao
only (this does not takes as long as the gcc+glibc combo :) ).
The reason for not going the host-provided java route is that I find it
troublesome to add logic to the recipe to find the java's class library
in case it is host provided or self-built.
Regards
Robert
Robert Schuster schrieb:
> Hi,
> since I've gotten r/w access to the repo (thanks again!) I have begun to
> slowly merge the Jalimo recipes. It all starts with this one:
>
> http://bugs.openembedded.org/show_bug.cgi?id=3457
>
> The recipe that builts the initial Java5-capable Java compiler.
>
> Please comment on the bug and tell me whether it should go in or what
> you would like to see changed.
>
> Regards
> Robert
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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 --]
prev parent reply other threads:[~2007-12-19 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 18:42 RFC: merging recipes from Jalimo Robert Schuster
2007-12-12 13:29 ` Leon Woestenberg
2007-12-12 16:01 ` Robert Schuster
2007-12-12 21:13 ` Paul Sokolovsky
2007-12-15 13:30 ` Leon Woestenberg
2007-12-19 13:54 ` Robert Schuster [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=476922B1.4090102@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.