java staging problem

java staging problem

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

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. How should we solve this in OE
properly? It's a shame that such great work on java suffers from small
bugs like this.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMLGgBMkyGM64RGpERAiXJAKCmUX9rBgLtY/WVypm1euj+EmoafwCbBMFX
XnVkSLR7mt3ZO1ZEJ5mzNdQ=
=vpls
-----END PGP SIGNATURE-----

Re: java staging problem

[Stefan Schmidt]

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.

regards
Stefan Schmidt

Re: java staging problem

[Koen Kooi]

-----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-----

Re: java staging problem

[Stefan Schmidt]

Hello.

On Thu, 2010-07-01 at 13:22, Koen Kooi wrote:
> > 
> > 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.

Good. Lets work on a cleaner solution once build problems have been settled.

regards
Stefan Schmidt

Re: java staging problem

[Henning Heinold]

Hi,

the problem is in java-library.bbclass which defines it's own stage.

The quickest solution is to add 

do_stage_append() {
	oe_jarinstall -s serializer-${PV}.jar serializer.jar
}

to the xalan recipe will do it after the Email.

The best solution is to remove the do_stage from java-library.bbclass
and teach the new staging system to put the java.jars into the nonearch-java-sysroot.

As Marcin pointed out earlier staging the jar's under arch-sysroot breaks
building whith multiple-archs in the same tmp-dir.

Bye Henning

PS: Seems I didn't hit this because of all my building machine has xalan installed from os.