|
[meta-security][PATCH 1/2] suricata: unify volatiles file name
Yi Zhao
Make the volatiles file name starts with digital.
Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-ids/suricata/suricata_4.1.9.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-ids/suricata/suricata_4.1.9.bb b/recipes-ids/suricata/suricata_4.1.9.bb index 135871c..3f7beaa 100644 --- a/recipes-ids/suricata/suricata_4.1.9.bb +++ b/recipes-ids/suricata/suricata_4.1.9.bb @@ -55,7 +55,7 @@ do_install_append () { oe_runmake install-rules DESTDIR=${D} install -d ${D}${sysconfdir}/suricata ${D}${sysconfdir}/default/volatiles - install -m 0644 ${WORKDIR}/volatiles.03_suricata ${D}${sysconfdir}/default/volatiles/volatiles.03_suricata + install -m 0644 ${WORKDIR}/volatiles.03_suricata ${D}${sysconfdir}/default/volatiles/03_suricata install -m 0644 ${S}/threshold.config ${D}${sysconfdir}/suricata -- 2.17.1
|
|
|
|
Re: QA notification for completed autobuilder build (yocto-3.2.rc2)
Sangeeta Jain
Hello all,
toggle quoted messageShow quoted text
This is the full report for yocto-3.2.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No new defects are found. No high milestone defects. Bugs verified: BUG id:14106 - [QA 3.2 RC1] failure in ptest : glib-2.0.glib/gdatetime.test Verified Fixed. Existing bugs observed in this release: BUG id:14051 - [QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind Updated with 17 ptests passed, 1 ptest still failing No new failures. ======= Bugs ======== https://bugzilla.yoctoproject.org/show_bug.cgi?id=14106 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051 Thanks, Sangeeta
-----Original Message-----
|
|
|
|
Install Yocto image and backup
JH
Apology if it is an off topic, I could not find proper mailing lists
to ask questions. I built Yocto Linux kernel and installed Yocto image to MTD NAND storage in an iMAX6 device, because we designed RO for the kernel and root file system, RW for applications, we can update applications OTA but we cannot update kernel and root file system OTA. My supervisor asked if we need to have a dual NAND storage to backup the kernel and root file image, if the NAND bad sector occurred in the primary image, it can be booted from the secondary backup image. I understand where the concerns come from, but I am not clear if it is necessary or if it is a common practice to perform NAND backup storage, appreciate your insight advice. Thank you very much. Kind regards, - jupiter
|
|
|
|
Re: Meta-java - openjdk-8-native - fatal error: sys/sdt.h: No such file or directory
I have bumbled into a few recipes like that as well. It caused some concern because bitbake is supposed to avoid contamination like that. You can use the ERROR_QA variable to do compile-host-path and install-host-path checks in your distro config. That should produce errors when something like your issue happens. ..Ch:W..
On Fri, Oct 30, 2020 at 8:56 AM Darcy Watkins <dwatkins@...> wrote:
-- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
|
|
|
Re: Meta-java - openjdk-8-native - fatal error: sys/sdt.h: No such file or directory
Darcy Watkins
Hi,
My host OS has systemtap-sdt-devel installed for some reason. I temporarily renamed the sdt.h to get it out of the way and the build worked.
If all I have to do is remove that package (and hopefully not need something that depends on it) then that works out OK.
On the other hand, this could be an indication that when building openjdk-8-native, the recipe is not properly distinguishing the native (target) sysroot versus the host sysroot (for the GCC on the system). Or the fact that the buildtools are used doesn’t prevent it from still checking the host system’s sysroot.
For now, the answer is don’t have systemtap-sdt-devel on your CentOS7 system (or use a docker container without it).
Regards,
Darcy
Darcy Watkins :: Senior Staff Engineer, Firmware
SIERRA WIRELESS Direct +1 604 233 7989 :: Fax +1 604 231 1109 :: Main +1 604 231 1100 13811 Wireless Way :: Richmond, BC Canada V6V 3A4 [M4]
From: Darcy Watkins <dwatkins@...>
Hi,
Openjdk-8-native breaks due to some mixup related to sdt.h not found
Dunfell branch built on CentOS7 with the buildtools installed.
This is first attempt with dunfell. Warrior built openjdk-8-native OK
I remember seeing something like this long ago but I don’t remember the fix.
--------
| /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/src/share/vm/utilities/dtrace.hpp:31:10: fatal error: sys/sdt.h: No such file or directory | 31 | #include <sys/sdt.h> | | ^~~~~~~~~~~ | compilation terminated. | make[6]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/makefiles/vm.make:310: precompiled.hpp.gch] Error 1 | make[5]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/makefiles/top.make:119: the_vm] Error 2 | make[4]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/Makefile:284: product] Error 2 | make[3]: *** [Makefile:231: generic_build2] Error 2 | make[2]: *** [Makefile:177: product] Error 2 | make[1]: *** [HotspotWrapper.gmk:45: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/build/hotspot/_hotspot.timestamp] Error 2 | make: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga//make/Main.gmk:110: hotspot-only] Error 2 | WARNING: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/temp/run.do_compile.27136:1 exit 1 from 'exit 1' | ERROR: Task (/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/upstream/yocto/meta-java/recipes-core/openjdk/openjdk-8-native_272.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 973 tasks of which 966 didn't need to be rerun and 1 failed.
Summary: 1 task failed: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/upstream/yocto/meta-java/recipes-core/openjdk/openjdk-8-native_272.bb:do_compile Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Regards,
Darcy
Darcy Watkins :: Senior Staff Engineer, Firmware
SIERRA WIRELESS Direct +1 604 233 7989 :: Fax +1 604 231 1109 :: Main +1 604 231 1100 13811 Wireless Way :: Richmond, BC Canada V6V 3A4 [M4]
|
|
|
|
Zeus to Dunfell package license checking change
Anders Montonen
Hi,
While upgrading our distro from Zeus to Dunfell, I ran into an issue where some locale packages blocked due to incompatible licenses, even though their licenses have not changed. For example, the license of libgnutls30 is “LGPLv2.1+", while the license for libgnutls-locale-fi is “GPLv3+ & LGPLv2.1+”. In Zeus, this combination was accepted, but not anymore. Is this intentional? I also think it’s a bit odd that the localization package has a different license than the library itself, though I haven’t looked if there’s anything explicitly said about this in the source code. Regards, Anders Montonen
|
|
|
|
Re: Yocto OS Creation on Linux Ubuntu 16.04 LTS
#yocto
Martin Jansa
This URL also fetches for me without any issues. If you cannot reach it from your location, you can still put an archive with it to your premirror or redirect it to some other repo accessible to you with something like: insteadOf = "git://git.kernel.org/pub/scm/network/iproute2/iproute2.git" in your .gitconfig. > Please let us know if there is any other alternative to install the Yocto OS or the Valgrind tool on Yocto OS. Normal iproute2 recipes are currently fetching tarball "${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz", the recipe you're using commes from some meta-intel-tsn layer: meta-intel-tsn/recipes-connectivity/iproute2/iproute2_git.bb:do_fetch which isn't even listed in https://layers.openembedded.org/, so first thing to fix your Yocto OS :) is to get rid of meta-intel-tsn or fix your networking.
On Fri, Oct 30, 2020 at 3:21 PM Sujan KS <katakam.sujan@...> wrote:
|
|
|
|
Re: Yocto OS Creation on Linux Ubuntu 16.04 LTS
#yocto
Sujan KS
Hi Thank you for your response.sorry missed to include yocto group list. I tried in two different networks , one is office n/w and other is personal n/w. Both ways I got the same issue. We could do it successively for the first time and later, we wanted to do it for the second time, because we need to include Valgrind in the config files so that we can run the Valgrind tool for our code. Please let us know if there is any other alternative to install the Yocto OS or the Valgrind tool on Yocto OS. Regards Sujan
On Fri, Oct 30, 2020 at 1:50 PM Josef Holzmayr <jester@...> wrote: For one thing, please keep the list on CC.
|
|
|
|
Re: Yocto OS Creation on Linux Ubuntu 16.04 LTS
#yocto
Josef Holzmayr
For one thing, please keep the list on CC.
Am Fr., 30. Okt. 2020 um 09:11 Uhr schrieb Sujan KS <katakam.sujan@...>: Second, I have just verified that the URL git://git.kernel.org/pub/scm/network/iproute2/iproute2.git perfectly clones here. So it might be a problem with your provider or some national firewall - another hint is: git.kernel.org[0: 147.75.46.191]: errno=Connection timed out git.kernel.org[1: 2604:1380:4080:c00::1]: errno=Network is unreachable But there's really nothing that we can do about it, sorry. It *IS* a network issue somewhere between you and the source repository. Greetz.
|
|
|
|
Re: Yocto OS Creation on Linux Ubuntu 16.04 LTS
#yocto
Josef Holzmayr
Just given the links a quick try here, it seems like your build is
toggle quoted messageShow quoted text
having connectivity issues. Please check you uplink, or if it is somehow filtered/proxied. Greetz Am Fr., 30. Okt. 2020 um 08:43 Uhr schrieb <katakam.sujan@...>:
|
|
|
|
Yocto OS Creation on Linux Ubuntu 16.04 LTS
#yocto
Sujan KS
We are facing issue in yocto OS creation due to time out issue and unable to create the image.
The log for this is as below,
WARNING: xf86-video-intel-2_2.99.917-r0 do_fetch: Failed to fetch URL git://anongit.freedesktop.org/xorg/driver/xf86-video-intel;branch=master, attempting MIRRORS if available
WARNING: xf86-video-ast-2_1.1.5-r0 do_fetch: Failed to fetch URL http://xorg.freedesktop.org/releases/individual/driver/xf86-video-ast-1.1.5.tar.bz2, attempting MIRRORS if available WARNING: xinit-1_1.4.1-r0 do_fetch: Failed to fetch URL http://xorg.freedesktop.org/releases/individual/app/xinit-1.4.1.tar.bz2, attempting MIRRORS if available WARNING: cwautomacros-native-20110201-r0 do_fetch: Failed to fetch URL https://downloads.sourceforge.net/cwautomacros.berlios/cwautomacros-20110201.tar.bz2, attempting MIRRORS if available WARNING: intel-microcode-20190618-r0 do_fetch: Failed to fetch URL git://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git;protocol=https, attempting MIRRORS if available WARNING: lvm2-2.03.02-r0 do_fetch: Failed to fetch URL ftp://sources.redhat.com/pub/lvm2/releases/LVM2.2.03.02.tgz, attempting MIRRORS if available WARNING: xdpyinfo-1_1.3.2-r0 do_fetch: Failed to fetch URL http://xorg.freedesktop.org/releases/individual/app/xdpyinfo-1.3.2.tar.bz2, attempting MIRRORS if available WARNING: xhost-1_1.0.8-r0 do_fetch: Failed to fetch URL http://xorg.freedesktop.org/releases/individual/app/xhost-1.0.8.tar.bz2, attempting MIRRORS if available WARNING: linux-firmware-1_0.0+gitAUTOINC+711d3297ba-r0 do_fetch: Failed to fetch URL git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git, attempting MIRRORS if available WARNING: dpkg-1.19.4-r0 do_fetch: Failed to fetch URL http://ftp.debian.org/debian/pool/main/d/dpkg/dpkg_1.19.4.tar.xz, attempting MIRRORS if available WARNING: iproute2-1.0-gitAUTOINC+97864a5af3-r0 do_fetch: Failed to fetch URL git://git.kernel.org/pub/scm/network/iproute2/iproute2.git, attempting MIRRORS if available ERROR: iproute2-1.0-gitAUTOINC+97864a5af3-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-owimWyNVWV"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/pdl/yocto_build/scripts:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot/usr/bin/crossscripts:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot-native/usr/sbin:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot-native/usr/bin:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot-native/sbin:/home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/recipe-sysroot-native/bin:/home/user/pdl/yocto_build/bitbake/bin:/home/user/pdl/yocto_build/build/tmp-glibc/hosttools"; export HOME="/home/user"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://git.kernel.org/pub/scm/network/iproute2/iproute2.git /home/user/pdl/yocto_build/build/downloads/git2/git.kernel.org.pub.scm.network.iproute2.iproute2.git --progress failed with exit code 128, output: Cloning into bare repository '/home/user/pdl/yocto_build/build/downloads/git2/git.kernel.org.pub.scm.network.iproute2.iproute2.git'... fatal: unable to connect to git.kernel.org: git.kernel.org[0: 147.75.46.191]: errno=Connection timed out git.kernel.org[1: 2604:1380:4080:c00::1]: errno=Network is unreachableERROR: iproute2-1.0-gitAUTOINC+97864a5af3-r0 do_fetch: Fetcher failure for URL: 'git://git.kernel.org/pub/scm/network/iproute2/iproute2.git'. Unable to fetch URL from any source. ERROR: iproute2-1.0-gitAUTOINC+97864a5af3-r0 do_fetch: ERROR: iproute2-1.0-gitAUTOINC+97864a5af3-r0 do_fetch: Function failed: base_do_fetch ERROR: Logfile of failure stored in: /home/user/pdl/yocto_build/build/tmp-glibc/work/corei7-64-oe-linux/iproute2/1.0-gitAUTOINC+97864a5af3-r0/temp/log.do_fetch.25170 ERROR: Task (/home/user/pdl/yocto_build/meta-intel-tsn/recipes-connectivity/iproute2/iproute2_git.bb:do_fetch) failed with exit code '1' NOTE: Tasks Summary: Attempted 3220 tasks of which 0 didn't need to be rerun and 1 failed.Summary: 1 task failed: /home/user/pdl/yocto_build/meta-intel-tsn/recipes-connectivity/iproute2/iproute2_git.bb:do_fetch Summary: There were 38 WARNING messages shown. Summary: There were 4 ERROR messages shown, returning a non-zero exit code. Anyone faced similar issue, please help us resolving this issue.
|
|
|
|
Re: musl and reproducible builds
Andrei Gherzan
Hi Khem,
30 Oct 2020 05:56:04 Khem Raj <raj.khem@...>: Hi AndreiThat's exactly what I ended up doing and it works just like glibc. Thanks for pushing the patch. -- Andrei Gherzan gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
|
|
|
|
Re: musl and reproducible builds
Hi Andrei
toggle quoted messageShow quoted text
I have posted a patch for master, please test it out and let me know if it fixes the issue. https://patchwork.openembedded.org/patch/177717/
On Thu, Oct 29, 2020 at 6:52 PM Khem Raj <raj.khem@...> wrote:
|
|
|
|
[meta-zephyr][PATCH] zephyr-kernel-test: drop fatal kernel testcase
Naveen Saini
kernel 'fatal' testcase has directory structure changes in v2.4.0
version, which does not fit in current meta-zephyr test build structure. So excluding it for now. Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc index faf28bd..a1e62af 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc @@ -25,7 +25,6 @@ ZEPHYRTESTS = " \ context \ device \ early_sleep \ - fatal \ fifo \ fpu_sharing \ gen_isr_table \ -- 2.17.1
|
|
|
|
Re: musl and reproducible builds
Hi Andrei
toggle quoted messageShow quoted text
Thanks for the report. What will help is linker command details to find more details but I know this issue is not addressed for musl yet so your analysis is right, I will see if I can fix it if no one else beats me to it and I have time which is scarce these days. regardless please open a bug in Bugzilla so we do not forget it. Thanks -Khem
On Thu, Oct 29, 2020 at 3:53 PM Andrei Gherzan <andrei@...> wrote:
|
|
|
|
musl and reproducible builds
Andrei Gherzan
Hi, I've hit lately a known issue regarding reproducible builds for which we added a workaround in the case of having glibc as the libc provider[1]. Some context. ARM binaries in a Yocto build contain references to the absolute path of libc C runtime objects `crti.o` and `crtn.o`. Here is an example: readelf -sW helloworld | grep crt [...] 35: 00000000 0 FILE LOCAL DEFAULT ABS [...]/yocto//tmp/work/armv7vet2hf-neon-poky-linux-musleabi/hello/1.0-r0/recipe-sysroot/usr/lib/crti.o 38: 00000000 0 FILE LOCAL DEFAULT ABS [...]/yocto//tmp/work/armv7vet2hf-neon-poky-linux-musleabi/hello/1.0-r0/recipe-sysroot/usr/lib/crtn.o After stripping the respective binary, these paths end up into the debug symbols but the stripped binary still contains the `.gnu_debuglink` section. This section includes, along with the filename of the debugging information file, a CRC value computed on the respective debugging file[2]. This CRC value makes, in turn, the stripped binary, not reproducible. IA platforms are not affected by this issue. I am looking for a fix/workaround when using musl as the libc provider. The fix mentioned above for glibc landed in `thud` so since then, this bug is mitigated when using glibc. But, when musl is preferred, the issue is still reproducible on current master's HEAD[3]. This behaviour can easily be reproduced using the qemuarm/qemux86 machines along with a dummy recipe like the one in our documentation[4]. Has anyone looked into this in the past? It very much sounds to me like a linker bug. [1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cd158dd197a3a41a91679107a94c6f213476921c [3] 7231c104303f72c5d72f837de114d4f5a633c7cd [4] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/documentation/ref-manual/examples/hello-single Regards, -- Andrei
|
|
|
|
Re: #yocto
#yocto
mail@...
Hey, Yes it got changed to make it clear that it has to be unique. You will get slot of fun when updating to dunfell. Also each recipes will have its own sysroot. Cheers
On Oct 29, 2020 20:37, "Monsees, Steven C (US) via lists.yoctoproject.org" <steven.monsees=baesystems.com@...> wrote:
|
|
|
|
Re: #yocto
#yocto
Monsees, Steven C (US)
Maybe the better question is, Does the BBFILE_COLLECTIONS name add now have to be unique ? In this scenario the BBFILE_COLLECTIONS name is currently set to += "intel" for both the respective layer.conf files... Currently under the "rocko" release this does not cause an isuue. Thanks, Steve
|
|
|
|
#yocto
#yocto
Monsees, Steven C (US)
I am currently looking at porting from “rocko” to “zeus”…
Under your migration pages, I saw that in the project 2.7 release the following change occurred to BitBake:
“Bitbake now checks BBFILE_COLLECTIONS for duplicate entries and triggers an error if any are found.”
Does this imply that Yocto/BitBake would now throw a “duplicate BBFILE_COLLECTIONS”, if say prior to 2.7 one had 2 layers such as:
(1) ./workspace_1/poky/../meta-intel (2) ./workspace_1/poky/../meta-1/meta-2/meta-intel
Where #1 was the actual meta-intel recipe, and #2 was for modification/configuration of #1 ?
Thanks, Steve
|
|
|
|
Meta-java - openjdk-8-native - fatal error: sys/sdt.h: No such file or directory
Darcy Watkins
Hi,
Openjdk-8-native breaks due to some mixup related to sdt.h not found
Dunfell branch built on CentOS7 with the buildtools installed.
This is first attempt with dunfell. Warrior built openjdk-8-native OK
I remember seeing something like this long ago but I don’t remember the fix.
--------
| /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/src/share/vm/utilities/dtrace.hpp:31:10: fatal error: sys/sdt.h: No such file or directory | 31 | #include <sys/sdt.h> | | ^~~~~~~~~~~ | compilation terminated. | make[6]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/makefiles/vm.make:310: precompiled.hpp.gch] Error 1 | make[5]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/makefiles/top.make:119: the_vm] Error 2 | make[4]: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga/hotspot/make/linux/Makefile:284: product] Error 2 | make[3]: *** [Makefile:231: generic_build2] Error 2 | make[2]: *** [Makefile:177: product] Error 2 | make[1]: *** [HotspotWrapper.gmk:45: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/build/hotspot/_hotspot.timestamp] Error 2 | make: *** [/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/jdk8u-jdk8u272-ga//make/Main.gmk:110: hotspot-only] Error 2 | WARNING: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/build/tmp/work/x86_64-linux/openjdk-8-native/272-r0/temp/run.do_compile.27136:1 exit 1 from 'exit 1' | ERROR: Task (/home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/upstream/yocto/meta-java/recipes-core/openjdk/openjdk-8-native_272.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 973 tasks of which 966 didn't need to be rerun and 1 failed.
Summary: 1 task failed: /home/dwatkins/workspace/zeta/upgrade-yocto_mg90-MG-os/upstream/yocto/meta-java/recipes-core/openjdk/openjdk-8-native_272.bb:do_compile Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Regards,
Darcy
Darcy Watkins :: Senior Staff Engineer, Firmware
SIERRA WIRELESS Direct +1 604 233 7989 :: Fax +1 604 231 1109 :: Main +1 604 231 1100 13811 Wireless Way :: Richmond, BC Canada V6V 3A4 [M4]
|
|
|