From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb
Date: Wed, 24 Aug 2011 20:25:45 +0200 [thread overview]
Message-ID: <j33fn9$b50$2@dough.gmane.org> (raw)
In-Reply-To: <CA+M6bXnG5iaUuv=60=cXGqACXzmnFL0PpGMkhUcbMNzsy+TnmQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 24-08-11 19:40, Tom Rini schreef:
> On Wed, Aug 24, 2011 at 8:22 AM, Jesse Gilles <jgilles@multitech.com> wrote:
>> On Tue, 2011-08-23 at 13:16 -0400, George C. Huntington, III wrote:
>>> I suspect that the problem is happening earlier, classpath isn't building. the javac wrapper eats the return code from a java compile.
>>
>> If George is right, then the following patch to the javac wrapper script may fix the issue. It fixes building classpath as well as returns the error code if all javac attempts fail.
>>
>> http://patches.openembedded.org/patch/9521/
>
> So... someone needs to get that into either oe.dev master or better yet update the java bits for meta-oe.
I've been thinking about a meta-java but haven't had the time to look into that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOVUIpMkyGM64RGpERAmLMAKCEA6PF88wNabEaccDjVXgAsIwzZwCfXi8g
KgAQpseUwf5yuMmx4aAF/Fw=
=R2Wu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-24 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 12:13 [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb Steffen Sledz
2011-08-19 14:30 ` Steffen Sledz
2011-08-23 7:28 ` Steffen Sledz
2011-08-23 7:35 ` Robert Schuster
2011-08-23 7:49 ` Steffen Sledz
2011-08-23 17:16 ` George C. Huntington, III
2011-08-24 15:22 ` Jesse Gilles
2011-08-24 17:40 ` Tom Rini
2011-08-24 18:25 ` Koen Kooi [this message]
2011-08-25 10:59 ` Steffen Sledz
2011-08-25 14:09 ` Steffen Sledz
2011-08-30 10:51 ` Steffen Sledz
2011-08-30 12:30 ` Paul Menzel
2011-08-30 15:25 ` George C. Huntington, III
2011-08-31 6:59 ` Steffen Sledz
2011-08-31 14:25 ` Jesse Gilles
2011-08-31 6:51 ` Robert Schuster
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='j33fn9$b50$2@dough.gmane.org' \
--to=koen@dominion.thruhere.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.