[yocto] [meta-cgl][PATCH] pacemaker: 1.1.13 -> 1.1.15
1) Upgrade pacemaker from 1.1.13 to 1.1.15.
2) Modify patch, since the data has been changed.
0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
Signed-off-by: Wang Xin
---
.../0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch | 2 +-
.../pacemaker/{pacemaker_1.1.13.bb => pacemaker_1.1.15.bb}| 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
rename meta-cgl-common/recipes-cgl/pacemaker/{pacemaker_1.1.13.bb =>
pacemaker_1.1.15.bb} (96%)
diff --git
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
index 0831fda..3104512 100755
---
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
+++
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
@@ -27,7 +27,7 @@ index 08b4611..6fcd1aa 100644
dnl Eventually remove this
if test "$cross_compiling" != "yes"; then
-- CFLAGS="$CFLAGS -I${prefix}/include/heartbeat"
+- CPPFLAGS="$CPPFLAGS -I${prefix}/include/heartbeat"
+ CFLAGS="$CFLAGS -I${STAGING_INCDIR}/heartbeat"
+ CPPFLAGS="$CPPFLAGS -I${STAGING_INCDIR}/heartbeat"
fi
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
similarity index 96%
rename from meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
rename to meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
index d2e2395..17c9fe4 100755
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
@@ -23,8 +23,8 @@ SRC_URI =
"https://github.com/ClusterLabs/${PN}/archive/Pacemaker-${PV}.zip \
file://volatiles \
file://tmpfiles \
"
-SRC_URI[md5sum] = "d84a5173306727a981a4f87e36007595"
-SRC_URI[sha256sum] =
"e963bc59a5d98a3e3441ea5cccb42aa67f9d7934b80c8818e19ae91c5da48331"
+SRC_URI[md5sum] = "3721971f8adba248076b43f97c4571ab"
+SRC_URI[sha256sum] =
"0787cbc18d1f1b360a11eb7ccb6714042360d4948b2517a9fe43daf9e839af66"
inherit autotools-brokensep pkgconfig systemd python-dir useradd
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [openCV] error during do_configure
I have added the openCV to my image (core-image-weston with buildessentials) and during the bitbake error appeard. Do you have any idea what should I do now to correctly install openCvV to my image? Part of the error: | -- Configuring incomplete, errors occurred! | See also "/home/admin/Zynq/poky/build/tmp/work/i586-poky-linux/opencv/3.1+gitAUTOINC+92387b1ef8-r0/build/CMakeFiles/CMakeOutput.log". | See also "/home/admin/Zynq/poky/build/tmp/work/i586-poky-linux/opencv/3.1+gitAUTOINC+92387b1ef8-r0/build/CMakeFiles/CMakeError.log". | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/admin/Zynq/poky/build/tmp/work/i586-poky-linux/opencv/3.1+gitAUTOINC+92387b1ef8-r0/temp/log.do_configure.30275) ERROR: Task 278 (/home/admin/Zynq/poky/meta-openembedded/meta-oe/recipes-support/opencv/ opencv_3.1.bb, do_configure) failed with exit code '1' -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel too old with core-image-minimal for Pine64
Hi Montez, On Sun, 21 Aug 2016 11:27:12 Mont3z Claros wrote: > I'm working on a bsp layer for SBC Pine64 and my image is successfully > generated but I'm getting "FATAL: kernel too old" when booting the > rootfs init. > > My kernel is version 3.10 and I used Linaro 5.3 to compile all > components of the image. I've tried adding: OLDEST_KERNEL = "3.10" and > I also try using Linaro 4.9 but I still get the same error. When you say you've tried adding OLDEST_KERNEL, where did you set that? Another thing to note - conf/bitbake.conf sets OLDEST_KERNEL_aarch64 = "3.14", and since on Pine64 that override would presumably apply, unless you are also using an override when you set your value I would strongly suspect your value is being overridden. Run bitbake -e | less and then search for OLDEST_KERNEL with / to confirm - you'll be able to see not just the final value but the history of how the value got set. To avoid this you'll likely need to set your OLDEST_KERNEL value with an override - the machine name should work i.e. assuming your MACHINE is "pine64" you would do: OLDEST_KERNEL_pine64 = "3.10" Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ac_cv_sizeof_long size definition by SDK
Hello.
I further gathered info and filed bellow.
(This is the first time I file a case against yoctoproject bugzilla, so please
point me if anything is not in convention.)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10255
From: Mark Hatle
Sent: Friday, September 9, 2016 11:46 PM
To: Takashi Matsuzawa; yocto@yoctoproject.org
Subject: Re: [yocto] ac_cv_sizeof_long size definition by SDK
On 9/9/16 6:33 AM, Takashi Matsuzawa wrote:
> Hello, Yocto.
>
>
> I am now puzzled by this variable ste in $CONFIG_SITE setup file in
> Yocto-generated SDK.
>
>
> I generated x86_64 host, arm (32bit) target SDK.
>
> And if I invoke $CC (arm-poky-linux-gnueabi-gcc), using this SDK, sizeof
> (long)
> is 4 (long = int)
>
>
> However, if I look into $CONFIG_SITE's definition of ac_cv_sizeof_long, it is
> defined as '8'.
>
> I feel this is strange since if this cached configure data is for the target
> (and cross-compiling), this value should be 4, to match the above
> (arm-poky-linux-gnueabi-gcc) result.
>
> (I think this part of the cache is being copied from
> poky/meta/site/x86_64-linux, )
There should be multiple caches. There may be one for the host (nativesdk) and
one for each target (arm 32-bit).
Once you load the environment file for the arm system, the CONFIG_SITE setting
should point to the proper settings for the environment file you have loaded.
In a Power (32-bit) SDK I had laying around:
sourcing "environment-setup-powerpc-linux"
results in:
CONFIG_SITE=.../sdk/site-config-powerpc-linux
if I look at that file:
ac_cv_sizeof_long=${ac_cv_sizeof_long=4}
which is the correct value.
If this is NOT what you are seeing in your generated SDKs, and you are loading
the proper environment file, please file a defect with the Yocto Project
version, your configuration information and a way to reproduce the problem.
--Mark
>
> This is causing break if I build autotool based program using the SDK.
>
>
> Am I doing mis-use of SDK here?
>
>
>
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package VersionUpstream version Maintainer NoUpgradeReason - --- -- python3-setuptools22.0.5 27.1.2Alejandro Hernandez python-git2.0.7 2.0.8 Alejandro Hernandez python-setuptools 22.0.5 27.1.2Alejandro Hernandez python3-numpy 1.11.0 1.11.1Alejandro Hernandez nfs-utils 1.3.3 1.3.4 Alejandro Hernandez perl 5.22.1 5.24.1Alejandro Hernandez python-pexpect4.2.0 4.2.1 Alejandro Hernandez python3-git 2.0.7 2.0.8 Alejandro Hernandez swig 3.0.8 3.0.10Alejandro Hernandez texinfo 6.06.3 Alejandro Hernandez perl-native 5.22.1 5.24.1Alejandro Hernandez liberation-fonts 1.04 2.00.1Alexander Kanavin 2.x depends on fontforge pa... dtc 1.4.1+gitX 1.4.2+gitAUTOINC+... Alexander Kanavin sysprof 3.20.0+gitX3.21.91+gitAUTOIN... Alexander Kanavin btrfs-tools 4.7.1 4.7.2 Alexander Kanavin openssl 1.0.2h 1.1.0 Alexander Kanavin cmake-native 3.6.1 3.6.2 Alexander Kanavin gnutls3.5.3 3.5.4 Alexander Kanavin cmake 3.6.1 3.6.2 Alexander Kanavin mkelfimage4.0+gitX 4.4+gitAUTOINC+58... Alexander Kanavin mkelfimage has been removed... libksba 1.3.4 1.3.5 Alexander Kanavin kexec-tools 2.0.12 2.0.13Alexander Kanavin dpkg 1.18.7 1.18.10 Aníbal Limón pinentry 0.9.2 0.9.7 Armin Kuster guilt-native 0.35+gitX 0.36+gitAUTOINC+2... Bruce Ashfield util-linux2.28.1 2.28.2Chen Qi systemd 230+gitX 231+gitAUTOINC+38... Chen Qi curl 7.50.1 7.50.2Chen Qi dbus-glib 0.106 0.108 Chen Qi diffutils 3.43.5 Chen Qi gawk 4.1.3 4.1.4 Chen Qi systemd-boot 230+gitX 231+gitAUTOINC+38... Chen Qi build-appliance-i... 15.0.0 15.0.1Cristian Iorga ltp 20160126 20160510 Dengke Du sgmlspl-native1.1+gitX 1.03+gitAUTOINC+f... Dengke Du linuxdoc-tools-na... 0.9.69 0.9.72Dengke Du chkconfig 1.3.58 1.8 Dengke Du Version 1.5 requires selinux u-boot-fw-utils v2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-boot-mkimagev2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-bootv2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko createrepo0.4.11 0.10.4Hongxu Jia Versions after 0.9.* use YU... elfutils 0.166 0.167 Hongxu Jia ncurses 6.0+20160625 6.0+20160910 Hongxu Jia gnupg 2.1.14 2.1.15Hongxu Jia pango 1.40.1 1.40.2Jussi Kukkonen libinput 1.4.1 1.4.901 Jussi Kukkonen wayland 1.11.0 1.11.93 Jussi Kukkonen weston1.11.0 1.11.93 Jussi Kukkonen clutter-gst-3.0 3.0.18 3.0.20Jussi Kukkonen shared-mime-info 1.61.7 Jussi Kukkonen xf86-input-synaptics 1.8.3 1.8.99.1 Jussi Kukkonen libevdev 1.5.2 1.5.4 Jussi Kukkonen gtk+ 2.24.302.24.31 Jussi Kukkonen libxfont 1.5.1 1.5.2 Jussi Kukkonen cogl-1.0 1.22.0 1.22.2Jussi Kukkonen freetype 2.6.5 2.7 Jussi Kukkonen mesa 12.0.1
Re: [yocto] Problem with exporting variable in bbappend file
Hi Raj Thanks for your reply. I tried bitbake-layers show-appends. I could see my bbappend file. But when I tried to grep the environment variable I am trying to set using bitbake -e, I am not able to see any output. Is there any way to confirm that the environment variable is set to the value I am trying to set ? Regards, Hari Prasath From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Tuesday, September 06, 2016 11:49 PM To: Gujulan Elango, Hari Prasath (H.) Cc: yocto@yoctoproject.org Subject: Re: [yocto] Problem with exporting variable in bbappend file On Aug 30, 2016, at 5:30 AM, Gujulan Elango, Hari Prasath (H.) wrote: Hello all, We are working on a platform based on Renesas processor. The BSP provided by them has arm-trusted-firmware. Now in order to enable all the 8 cores, they have suggested to add a environment variable in the arm-trusted-firmware_git.bb file in their BSP layer as below. export PSCI_DISABLE_BIGLITTLE_IN_CA57BOOT="0" We would prefer to make this change in our custom layer by creating a .bbappend file. We added the change in bbappend file, recompiled it and tested, but couldn't get the expected results. When I do the same change in the .bb file itself in their BSP layer, I am able to see the expected result. Is it okay to just add the export as mentioned above in the .bbappend file ? Am I missing something else ? ensure that your bbappend is actually applying to the final parsed recipe. You can use bitbake-layers show-appends to ensure that or simply bitbake -e and grep for this change Thanks & Regards, Hari Prasath -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
