Good day all;

Short version:
I'm trying to add the meta-oracle-java layer to a working, plain vanilla 
meta-raspberrypi layer build. Unfortunately, I'm not having any success. Any 
guidance, suggestions or pointers would be most appreciated.

Long version:
First off, I'm a complete newbie to the Yocto ecosystem so please turn on your 
filters and be gentle.  ;-)

***** Step 1 *****
I have successfully config-ed, built and run on RPi2 HW a plain vanilla 
meta-raspberrypi layer build using the guidance from...
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/about/
adjusted the default conf/local.conf to contain...
MACHINE ?= "raspberrypi2"
INHERIT += "rm_work"
used the command...
> bitbake rpi-hwup-image
and the following conf/bblayer.conf file...
<SOF>
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/mschnell/poky/meta \
  /home/mschnell/poky/meta-yocto \
  /home/mschnell/poky/meta-yocto-bsp \
  /home/mschnell/build-rpi/meta-raspberrypi \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /home/mschnell/poky/meta \
  /home/mschnell/poky/meta-yocto \
  "
<EOF>

***** Step 2 *****
However, when I add the meta-oracle-java layer to the conf/bblayers.conf file 
using guidance from...
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-oracle-java/about/
adjusting the default conf/local.conf to contain...
LICENSE_FLAGS_WHITELIST += "oracle_java"
PACKAGE_CLASSES = "package_deb"
and the following modified conf/bblayer.conf file...
<SOF>
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/mschnell/poky/meta \
  /home/mschnell/poky/meta-yocto \
  /home/mschnell/poky/meta-yocto-bsp \
  /home/mschnell/build-rpi/meta-raspberrypi \
  /home/mschnell/build-rpi/meta-oracle-java \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /home/mschnell/poky/meta \
  /home/mschnell/poky/meta-yocto \
  "
<EOF>
The bake...
> bitbake rpi-hwup-image

Build Configuration:
BB_VERSION        = "1.28.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "CentOS-Linux-7.2.1511"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "raspberrypi2"
DISTRO            = "poky"
DISTRO_VERSION    = "2.0.2"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard vfpv4 
cortexa7"
TARGET_FPU        = "vfp-vfpv4-neon"
meta
meta-yocto
meta-yocto-bsp    = "jethro:40376446904ae3529be41737fed9a0b650ed167d"
meta-raspberrypi  = "jethro:f2cff839f52a6e6211337fc45c7c3eabf0fac113"
meta-oracle-java  = "master:f44365f02b283c3fb362dc99e2e996d3f11e356e"
...results in an image file does _not_ have any java components in it. :(


***** Step 3 *****
In an attempt to determine that was happening I looked over the logs in...
> grep -i java tmp/log/cooker/raspberrypi2/20160818154951.log
There I noticed that there was one and only one 'java' string in the whole log 
file...
meta-oracle-java  = "master:f44365f02b283c3fb362dc99e2e996d3f11e356e"
...and _that_ certainly didn't seem right.  I was expecting a bunch of java, 
jdk and jre strings in the downloaded file names in the logs.

So I decided to try and build _just_ the meta-oracle-java layer via...
> bitbuild oracle-jse-jre
...and ah HA!  Error messages....
ERROR: Fetcher failure for URL: 
'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'.
 Checksum mismatch!
File: 
'/home/mschnell/build-rpi/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'
 has md5 checksum fe0826ca8ca01c88caaf5db3ad9f84a5 when 
b9b8f598b0a7f49e4d221f16ba25c6c0 was expected
File: 
'/home/mschnell/build-rpi/downloads/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'
 has sha256 checksum 
24d885d535739a6b7b54e153919fbbce932a344f5ca3ee5a86b01ac775085863 when 
ed061060011d88efe5563c2949c00993db85db17ab94f18a78713007a2b90faf was expected
If this change is expected (e.g. you have upgraded to a new version without 
updating the checksums) then you can use these lines within the recipe:
SRC_URI[md5sum] = "fe0826ca8ca01c88caaf5db3ad9f84a5"
SRC_URI[sha256sum] = 
"24d885d535739a6b7b54e153919fbbce932a344f5ca3ee5a86b01ac775085863"
Otherwise you should retry the download and/or check with upstream to determine 
if the file has become corrupted or otherwise unexpectedly modified.

ERROR: Function failed: Fetcher failure for URL: 
'http://download.oracle.com/otn/java/ejre/7u60-b19/ejre-7u60-fcs-b19-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/home/mschnell/build-rpi/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/oracle-jse-jre/1.8.0-u60r0/temp/log.do_fetch.30643
ERROR: Task 4 
(/home/mschnell/build-rpi/meta-oracle-java/recipes-devtools/oracle-java/oracle-jse-jre_1.8.0.bb,
 do_fetch) failed with exit code '1'

***** Step 4 *****
OK. Looking thru the recipes in meta-oracle-java:
> cd meta-oracle-java/recipes-devtools/oracle-java
I don't see an *arm*.bb file (although I'm not sure that I should. But there 
are *i586*.bb and *x86_64*.bb file.)
> ls
oracle-jse-jre-x86-64.inc
oracle-jse-jre.inc
oracle-jse-jre-i586.inc
oracle-jse-jre_1.8.0.bb
oracle-jse-jdk-x86-64_1.8.0.bb
oracle-jse-jdk.inc
oracle-jse-jdk-i586_1.8.0.bb
oracle-jse.inc
oracle-jse-ejre.inc
oracle-jse-ejre-arm-vfp-hflt-client-headless.inc
And the "architecture sensitive" parts of the .inc files seem to be pointing to 
different Java version.
> grep "SRC_URI =" *
oracle-jse-ejre-arm-vfp-hflt-client-headless.inc:SRC_URI = 
"http://download.oracle.com/otn/java/ejre/7u${PV_UPDATE}-b${BUILD_NUMBER}/ejre-7u${PV_UPDATE}-fcs-b${BUILD_NUMBER}-linux-arm-vfp-hflt-client_headless-07_may_2014.tar.gz";
oracle-jse-jdk-i586_1.8.0.bb:SRC_URI = 
"http://download.oracle.com/otn-pub/java/jdk/8u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-8u${PV_UPDATE}-linux-i586.tar.gz";
oracle-jse-jdk-x86-64_1.8.0.bb:SRC_URI = 
"http://download.oracle.com/otn-pub/java/jdk/8u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-8u${PV_UPDATE}-linux-x64.tar.gz";
oracle-jse-jre-i586.inc:SRC_URI = 
"http://download.oracle.com/otn-pub/java/jdk/8u${PV_UPDATE}-b${BUILD_NUMBER}/jre-8u${PV_UPDATE}-linux-i586.tar.gz";
oracle-jse-jre-x86-64.inc:SRC_URI = 
"http://download.oracle.com/otn-pub/java/jdk/8u${PV_UPDATE}-b${BUILD_NUMBER}/jre-8u${PV_UPDATE}-linux-x64.tar.gz";
> grep "PV_UPDATE =" *
oracle-jse-ejre-arm-vfp-hflt-client-headless.inc:PV_UPDATE = "60"
oracle-jse-jdk-i586_1.8.0.bb:PV_UPDATE = "91"
oracle-jse-jdk-x86-64_1.8.0.bb:PV_UPDATE = "91"
oracle-jse-jre-i586.inc:PV_UPDATE = "91"
oracle-jse-jre-x86-64.inc:PV_UPDATE = "91"
> grep "BUILD_NUMBER =" *
oracle-jse-ejre-arm-vfp-hflt-client-headless.inc:BUILD_NUMBER = "19"
oracle-jse-jdk-i586_1.8.0.bb:BUILD_NUMBER = "14"
oracle-jse-jdk-x86-64_1.8.0.bb:BUILD_NUMBER = "14"
oracle-jse-jre-i586.inc:BUILD_NUMBER = "14"
oracle-jse-jre-x86-64.inc:BUILD_NUMBER = "14"

To my uneducated eye it seems that, although the meta-oracle-java layer 
purports to be at Java 8u91 build 14; this only seems to be the case for the 
i586 and x86_64 architectures and not for the ARM, which is at Java 7u60 build 
19.

I've been trying to update the ARM architecture to support Java v8u91 in the 
meta-oracle-java recipes, but have not yet been successful.


Bottom line:
I'm looking for anyone that has successfully added the meta-oracle-java layer 
to meta-raspberrypi.  Or, barring that, any ideas, suggestions or guidance for 
this wandering newbie.


Cheers....
--
-- I would like mornings better if they started later in the day. --
--  Mark Schnell   --   +1-919-407-4327   --   mschn...@cree.com  --


________________________________
This e-mail message, including any attachments and previous email messages sent 
with it, contains CONFIDENTIAL and PROPRIETARY information of Cree, Inc. or its 
subsidiaries and may be legally PRIVILEGED. You may not use, disclose, 
reproduce or distribute such information without Cree's authorization. If you 
have received this message in error, please notify the sender immediately and 
permanently delete the original message, its attachments and any copies thereof.
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to