[oe] Query on meta-java layer openjdk-7-jre build

[Colin Smiley]

Earlier this week, I’d sent an email to the list about my problems getting
openjdk-6 to build.

The short version of my build process is:

1) install poky on daisy branch
2) install open embedded on daisy branch
3) install meta-java on trunk
4) attempt to bitbake java-test-image (removing openjdk-7 line).
5) Wait for java CurrencyData failure, fix it manually.
6) re-reun bitbake java-test-image

At this point, my build fails running qemu-i36. The image will use up all
available memory on the system, and then get killed by the linux oom
killer. I have tried this on a variety of OS, VM, physical machine, and
memory combinations. The result is always the same.

Is the problem I’m seeing the same as what you’re describing below?

Also, is there an update to meta-java to fix the CurrencyData problem?


Thanks,


Colin

On 1/14/15, 6:11 PM, "Otavio Salvador" <otavio at ossystems.com.br> wrote:

>Hello,
>
>(I am adding Alex on Cc as well)
>
>On Wed, Jan 14, 2015 at 9:52 PM, Max Krummenacher <max.oss.09 at gmail.com>
>wrote:
>> Otavio Salvador <otavio <at> ossystems.com.br> writes:
>>>  Can you prepare a patchset for it?
>>>
>>
>> I'm not really convinced that reverting the static linking is a good
>> approach as obviously something failed when linking dynamically.
>>
>> Both mails which reported the issue with the failing qemu-arm run were
>>built
>> for colibri-t20. The Tegra T20 SOC is a bit special as it does not have
>>a
>> Neon unit. Plus our standard setup uses angstrom which builds the linaro
>> toolchain with thumb2 support.
>>
>> So the failing builds are failing with an unusual oe toolchain
>>configuration
>> and the root cause is the toolchain.
>> I'm unsure if risking the failing builds with dynamic linking poping up
>> again justifies fixing the build failures in an unusual configuration.
>>
>> If you don't think so I can prepare a patch, no problem.
>
>It is failing on me as well.
>
>Alex has found that QEMU -L command is causing issue so if your patch
>fixes it, it could be an option for sure.
>
>I think there's no good answer as a patch for test. :-) I think we all
>can try it and see if it improves it after all.
>
>-- 
>Otavio Salvador                             O.S. Systems
>http://www.ossystems.com.br        http://code.ossystems.com.br
>Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>-- 
>_______________________________________________
>Openembedded-devel mailing list
>Openembedded-devel at lists.openembedded.org
>http://lists.openembedded.org/mailman/listinfo/openembedded-devel