From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: java staging problem
Date: Thu, 01 Jul 2010 13:22:40 +0200 [thread overview]
Message-ID: <i0htq1$7dm$1@dough.gmane.org> (raw)
In-Reply-To: <20100701105500.GA12260@excalibur.local>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01-07-10 12:55, Stefan Schmidt wrote:
> Hello.
>
> On Thu, 2010-07-01 at 12:03, Koen Kooi wrote:
>>
>> I'm attempting to build openjdk using the jalimo overlay and I found a
>> problem with the staging dirs:
>>
>> /OE/angstrom-dev/sysroots/java <- contains a few jars e.g. xalan2.jar
>> /OE/angstrom-dev/sysroot/x86_64-linux/usr/share/java <- contains other
>> jars, e.g. serializer.jar
>>
>> The openjdk configure tells the buildsystem that both xalan2.jar and
>> serializer.jar are in /OE/angstrom-dev/sysroots/java when only
>> xalan2.jar is.
>>
>> I vaguely remember the buglabs people talking about that and their
>> local.conf mangles some JAVA vars.
>
> That is what we have in our local.conf:
>
> # Stage JAR files not into ARCH related dirs
> STAGING_DIR_JAVA = "${STAGING_DIR}/java"
> STAGING_DATADIR_JAVA ?= ${STAGING_DIR_JAVA}
>
> Full local.conf can be found here:
> http://svn.buglabs.net/svn/!source/11343/bug/trunk/com.buglabs.build.oe/build/conf/local.conf
>
>> How should we solve this in OE properly?
>
> That is a good question. So far I have mostly avoided the java building and left
> the honor to tarrent.
>
> Our build setup is a bit fragile right now as javac segfault sometimes during
> building and we don't know why. Another out of memory bug should be fixed by
> Henning again.
>
> Right now I would be happy to have a reliable build and then work towards
> getting it mor sane and bring it into OE. Thats blocking me a bit here from
> further upstream work, but we will get behind it.
I pushed all the magic needed to build it for angstrom:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=90249cc563b916a4d764573156042fd8998f0731
That should make it easier for other people to test.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMLHqAMkyGM64RGpERAtUyAJ9F5GdjHeYhnOuKZnndBKb9oVDWcACeKkme
alhGxNynaVqIPVYp9H6VEEg=
=wUSI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-01 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 10:03 java staging problem Koen Kooi
2010-07-01 10:55 ` Stefan Schmidt
2010-07-01 11:22 ` Koen Kooi [this message]
2010-07-01 11:30 ` Stefan Schmidt
2010-07-01 11:37 ` Henning Heinold
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='i0htq1$7dm$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.