Date   

Re: Build failure due to wic-tools dependency #yocto

Gujulan Elango , Hari Prasath
 

Update:

 I could able to see the e2fsprogs-native binaries generated under the below path.

build/tmp/sysroots-components/x86_64/e2fsprogs-native/sbin
 
The PATH variable in the file "build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/temp/run.do_image_wic.21626" is set to the following which doesn't include the above path.?Could it be that the yocto build system is unable to locate this binary ?
 
export PATH="/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot/opt/fsl-imx-wayland/5.4-zeus/sysroots/x86_64-pokysdk-linux/usr/bin/crossscripts:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/usr/bin/python3-native:/home/hari/projects/tx-nextgen/linux-yocto-bsp/sources/poky/scripts:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot/usr/bin/crossscripts:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/usr/sbin:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/usr/bin:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/sbin:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/recipe-sysroot-native/bin:/home/hari/projects/tx-nextgen/linux-yocto-bsp/sources/poky/bitbake/bin:/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/hosttools"



On Sat, Sep 5, 2020 at 8:17 PM hariprasath.gujulanelango via lists.yoctoproject.org <hariprasath.gujulanelango=wabco-auto.com@...> wrote:
Hi There

Thanks for your reply.As I already mentioned in my original post, this dependency is already present in the wic-tools BB file. The git log also shows the same as below

commit b139ac4910a8c519076eaa865d9b0b7d9e604833
Author: Ed Bartosh <ed.bartosh@...>
Date:   Thu Jul 27 09:54:04 2017 +0300
 
    wic-tools: add dependency to e2fsprogs-native
    
    Added e2fsprogs-native to the list of dependencies for wic-tools
    as all fs-related utilities have to be in this list.
    
    (From OE-Core rev: d0ebcf62109d6a131e02cd4c0f04bba203ed6579)
    
    Signed-off-by: Ed Bartosh <ed.bartosh@...>
    Signed-off-by: Richard Purdie <richard.purdie@...>





--
Best Regards,
Hari Prasath


Proprietary and confidential. It is for use by the addressee only. If you are not the addressee or If you received this email in error, please notify the sender and delete it and any attachments. All communications are subject to our Data Protection Policy that can be found at https://www.wabco-auto.com/en/footer/legal/legal/privacy-statement/ . By communicating with us via e-mail, you agree to the policy. WABCO does not guarantee that this email has not been intercepted, amended, or is virus-free. No liability is accepted for viruses and it is your responsibility to scan any attachments. Technical data and/or information provided in this email or any attachment may be subject to U.S. export control laws. Export, re-export, diversion or disclosure contrary to U.S. law is prohibited


bitbake recipe / Network UPS tool

Yocto
 

Okay heres the bitbake file, the archive manually extracts to, but if i run bitbake nut

SECTION = "console/network"

DESCRIPTION = "Network UPS Tools is a collection of programs which provide a common\
interface for monitoring and administering UPS, PDU and SCD hardware.\
It uses a layered approach to connect all of the parts."\

LICENSE = "GPLv3"

SRC_URI = "https://github.com/networkupstools/nut/archive/v2.7.4.tar.gz"

LIC_FILES_CHKSUM = "file://LICENSE-GPL3;md5=f27defe1e96c2e1ecd4e0c9be8967949"

SRC_URI[md5sum] = "81f5b97ed35fde35d57e1f87f23ad932"
SRC_URI[sha256sum] = "d580915fdf7090655c1c7c98eb116b61952553f06f0039b1f93c9f5a13e2d36b"

S = "${WORKDIR}/${PN}-${PV}"

#inherit autotools-brokensep
inherit autotools

EXTRA_OECONF = "--with-usb --with-serial --with-dev"


running bitbake nut i get this result

ERROR: nut-2.7.4-r0 do_configure: autoreconf execution failed.
ERROR: nut-2.7.4-r0 do_configure: Execution of '/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947' failed with exit code 1:
automake (GNU automake) 1.16.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <tromey@...>
       and Alexandre Duret-Lutz <adl@...>.
AUTOV is 1.16
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --system-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot/usr/share/aclocal/ --automake-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal-1.16 -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoconf --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoheader --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:19: installing './compile'
configure.ac:15: installing './missing'
clients/Makefile.am: installing './depcomp'
configure.ac:1268: error: required file 'scripts/augeas/nutupsconf.aug.in' not found
configure.ac:1268: error: required file 'scripts/devd/nut-usb.conf.in' not found
configure.ac:1268: error: required file 'scripts/udev/nut-usbups.rules.in' not found
autoreconf: automake failed with exit status: 1
WARNING: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947:301 exit 1 from 'exit 1'
WARNING: Backtrace (BB generated script):
    #1: bbfatal_log, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 301
    #2: die, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 246
    #3: autotools_do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 234
    #4: do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 150
    #5: main, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 305

Backtrace (metadata-relative locations):
    #1: bbfatal_log, /var/home/dingo/overc/poky/meta/classes/logging.bbclass, line 72
    #2: die, /var/home/dingo/overc/poky/meta/classes/base.bbclass, line 56
    #3: autotools_do_configure, /var/home/dingo/overc/poky/meta/classes/autotools.bbclass, line 232
    #4: do_configure, autogenerated, line 2
ERROR: Logfile of failure stored in: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/log.do_configure.635947
Log data follows:
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common']
| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function do_configure
| automake (GNU automake) 1.16.2
| Copyright (C) 2020 Free Software Foundation, Inc.
| License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl-2.0.html>
| This is free software: you are free to change and redistribute it.
| There is NO WARRANTY, to the extent permitted by law.
|
| Written by Tom Tromey <tromey@...>
|        and Alexandre Duret-Lutz <adl@...>.
| AUTOV is 1.16
| NOTE: Executing ACLOCAL="aclocal --system-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot/usr/share/aclocal/ --automake-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal-1.16" autoreconf -Wcross --verbose --install --force --exclude=autopoint -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal --system-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot/usr/share/aclocal/ --automake-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal-1.16 -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force -I m4
| autoreconf: configure.ac: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
| libtoolize: copying file './ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoconf --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
| autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoheader --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
| autoreconf: running: automake --add-missing --copy --force-missing
| configure.ac:19: installing './compile'
| configure.ac:15: installing './missing'
| clients/Makefile.am: installing './depcomp'
| configure.ac:1268: error: required file 'scripts/augeas/nutupsconf.aug.in' not found
| configure.ac:1268: error: required file 'scripts/devd/nut-usb.conf.in' not found
| configure.ac:1268: error: required file 'scripts/udev/nut-usbups.rules.in' not found
| autoreconf: automake failed with exit status: 1
| ERROR: autoreconf execution failed.
| WARNING: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947:301 exit 1 from 'exit 1'
| WARNING: Backtrace (BB generated script):
|     #1: bbfatal_log, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 301
|     #2: die, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 246
|     #3: autotools_do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 234
|     #4: do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 150
|     #5: main, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 305
| ERROR: Execution of '/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947' failed with exit code 1:
| automake (GNU automake) 1.16.2
| Copyright (C) 2020 Free Software Foundation, Inc.
| License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl-2.0.html>
| This is free software: you are free to change and redistribute it.
| There is NO WARRANTY, to the extent permitted by law.
|
| Written by Tom Tromey <tromey@...>
|        and Alexandre Duret-Lutz <adl@...>.
| AUTOV is 1.16
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal --system-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot/usr/share/aclocal/ --automake-acdir=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal-1.16 -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ -I /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force -I m4
| autoreconf: configure.ac: tracing
| autoreconf: running: libtoolize --copy --force
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
| libtoolize: copying file './ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoconf --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
| autoreconf: running: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/bin/autoheader --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4/m4/ --include=/var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/recipe-sysroot-native/usr/share/aclocal/ --force
| autoreconf: running: automake --add-missing --copy --force-missing
| configure.ac:19: installing './compile'
| configure.ac:15: installing './missing'
| clients/Makefile.am: installing './depcomp'
| configure.ac:1268: error: required file 'scripts/augeas/nutupsconf.aug.in' not found
| configure.ac:1268: error: required file 'scripts/devd/nut-usb.conf.in' not found
| configure.ac:1268: error: required file 'scripts/udev/nut-usbups.rules.in' not found
| autoreconf: automake failed with exit status: 1
| WARNING: /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947:301 exit 1 from 'exit 1'
| WARNING: Backtrace (BB generated script):
|     #1: bbfatal_log, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 301
|     #2: die, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 246
|     #3: autotools_do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 234
|     #4: do_configure, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 150
|     #5: main, /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/temp/run.do_configure.635947, line 305
|
| Backtrace (metadata-relative locations):
|     #1: bbfatal_log, /var/home/dingo/overc/poky/meta/classes/logging.bbclass, line 72
|     #2: die, /var/home/dingo/overc/poky/meta/classes/base.bbclass, line 56
|     #3: autotools_do_configure, /var/home/dingo/overc/poky/meta/classes/autotools.bbclass, line 232
|     #4: do_configure, autogenerated, line 2
ERROR: Task (/var/home/dingo/overc/meta-ups/recipes-support/nut/nut_2.7.4.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 528 tasks of which 527 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/var/home/dingo/overc/meta-ups/recipes-support/nut/nut_2.7.4.bb:do_configure
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

ls /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/
build  license-destdir  nut-2.7.4  recipe-sysroot recipe-sysroot-native  temp

and ls /var/home/dingo/overc/build/tmp/work/corei7-64-overc-linux/nut/2.7.4-r0/nut-2.7.4
aclocal.m4  autom4te.cache  compile       config.sub    COPYING docs     INSTALL      lib           ltmain.sh    Makefile.am NEWS     server       TODO
AUTHORS     clients         conf          configure     data drivers  INSTALL.nut  LICENSE-GPL2  m4           Makefile.in README   test-driver  tools
autogen.sh  common          config.guess  configure.ac  depcomp include  install-sh   LICENSE-GPL3  MAINTAINERS  missing scripts  tests        UPGRADING


Compiling and packaging libraries

majid.nasiry65@...
 

Hi
I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error.
I know default method for install libraries is versioned mode and I need to make symbolic links, but I don't know how?
Another question is what is difference between -dev and -dbg output? 

 


Re: Build failure due to wic-tools dependency #yocto

Gujulan Elango , Hari Prasath
 

Hi There

Thanks for your reply.As I already mentioned in my original post, this dependency is already present in the wic-tools BB file. The git log also shows the same as below

commit b139ac4910a8c519076eaa865d9b0b7d9e604833
Author: Ed Bartosh <ed.bartosh@...>
Date:   Thu Jul 27 09:54:04 2017 +0300
 
    wic-tools: add dependency to e2fsprogs-native
    
    Added e2fsprogs-native to the list of dependencies for wic-tools
    as all fs-related utilities have to be in this list.
    
    (From OE-Core rev: d0ebcf62109d6a131e02cd4c0f04bba203ed6579)
    
    Signed-off-by: Ed Bartosh <ed.bartosh@...>
    Signed-off-by: Richard Purdie <richard.purdie@...>



Re: Build failure due to wic-tools dependency #yocto

Khem Raj
 

it seems you might be missing below commit
https://git.openembedded.org/openembedded-core/commit/?id=d0ebcf62109d6a131e02cd4c0f04bba203ed6579

On Sat, Sep 5, 2020 at 12:17 AM
<hariprasath.gujulanelango@...> wrote:

Hello all

I am trying to build Yocto based distribution for a custom target based on I.MX8. While creating the target image, I am facing the below error. The wic-tools recipe file already has 'e2fsprogs-native' in its DEPENDS list. Also I am able to the see the e2fsprogs-native binaries generate already under "build/tmp/sysroots-components/x86_64/e2fsprogs-native/sbin/". I have attached the necessary logs for reference.

Additionally I tried 'bitbake wic-tools' and that builds fine. Any hints whats wrong ?

| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
|
| ERROR: A native program mkfs.ext4 required to build the image was not found (see details above).
|
| Please make sure wic-tools have e2fsprogs-native in its DEPENDS, build it with 'bitbake wic-tools' and try again.
|
|
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/temp/run.do_image_wic.21626' failed with exit code 1:
| INFO: Creating image(s)...
|
| ERROR: A native program mkfs.ext4 required to build the image was not found (see details above).
|
| Please make sure wic-tools have e2fsprogs-native in its DEPENDS, build it with 'bitbake wic-tools' and try again.
|
|
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/hari/projects/tx-nextgen/linux-yocto-bsp/sources/meta-tx-nextgen/recipes-core/images/nextgen-image.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5390 tasks of which 1 didn't need to be rerun and 1 failed.


Build failure due to wic-tools dependency #yocto

Gujulan Elango , Hari Prasath
 

Hello all

I am trying to build Yocto based distribution for a custom target based on I.MX8. While creating the target image, I am facing the below error. The wic-tools recipe file already has 'e2fsprogs-native' in its DEPENDS list. Also I am able to the see the e2fsprogs-native binaries generate already under "build/tmp/sysroots-components/x86_64/e2fsprogs-native/sbin/". I have attached the necessary logs for reference.

Additionally I tried 'bitbake wic-tools' and that builds fine. Any hints whats wrong ?

| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
| ERROR: A native program mkfs.ext4 required to build the image was not found (see details above).
| Please make sure wic-tools have e2fsprogs-native in its DEPENDS, build it with 'bitbake wic-tools' and try again.
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/hari/projects/tx-nextgen/linux-yocto-bsp/build/tmp/work/imx8mmddr4evk-poky-linux/nextgen-image/1.0-r0/temp/run.do_image_wic.21626' failed with exit code 1:
| INFO: Creating image(s)...
| ERROR: A native program mkfs.ext4 required to build the image was not found (see details above).
| Please make sure wic-tools have e2fsprogs-native in its DEPENDS, build it with 'bitbake wic-tools' and try again.
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/hari/projects/tx-nextgen/linux-yocto-bsp/sources/meta-tx-nextgen/recipes-core/images/nextgen-image.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5390 tasks of which 1 didn't need to be rerun and 1 failed.
 


Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020

Trevor Woerner
 

Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolly, Jan-Simon Möller, Alejandro H, Bruce
Ashfield, Armin Kuster, Richard Purdie, David Reyna, Steve Sakoman, Michael
Halstead, Ross Burton, Paul Barker, Mark Morton, Scott Murray, Jeremy
Puhlman, Joshua Watt, Jon Mason, Randy MacLeod

== notes ==
- entered m3 feature freeze
- working on a couple patches for 3.2
- bitbake server startup changed to avoid recently discovered issues will wait
for 3.3 to make default
- one more round of recipe upgrades before m3 build (later this week)
- -fno-common back to gcc10 default
- still some AB issues
- looking for help with unassigned bugs

== general ==
RP: list of 3.2 things:
Mark’s hash equivalency prserv fix
RP: where are we with bind?
Armin: haven’t gotten around to sending them
RP: please do so
RP: want to get more of the AUH upgrades in too.
RP: Alex has queued up the rest.
RP: high priority bitbake bug on startup that needs to go in
docs changes, we want to cut over to sphinx before m3

TrevorW: what’s the -fno-common issue?
RP: gcc changed defaults with gcc10, caused namespaces to overlap (and code
builds to fail), we temporarily switched away from the new default, waited
for upstream and created patches, now we can switch back to gcc10’s
default

Joshua: what still needs to be done with the docs?
RP: check Nico’s doc. right now: mostly marking up the code sections. please
coordinate on the mailing list

PaulB: will be giving a talk at the upcoming Linaro Connect on license
compliance with Yocto, Linaro Connect (virtual) is supposed to be free to
attend this year

RP: i’ve heard that YP was mentioned at last week’s Plumbers, does anyone
know when/where it could have been mentioned?
(various): not sure
Scott: I don’t see Khem here, maybe he was talking about it?
TrevorW: Alistair Francis is a contributor to YP and RISC-V, it could have
been brought up in relation to that. the RISC-V YP BSP carries a lot of
patches

Randy: Saul Wold is joining WR today!
RP: glad to hear he’s returning to YP


overide glib-2.0 meson.cross.d

Marek Belisko
 

Hello,

we're using dunfell poky release and we need to bump meson from 0.53.2
to 0.55 because of cuda cross compilation issues in 0.53.2. After bump
we start seeing build problem in glib-2.0 which was fixed in poky by
commit:

85d3e045bdec5c3649c55ea334969641382d7758 - glib-2.0: correct build
with latest meson

O overtook patch to my local meta layer but this is not simply working
cos meson.cross.d is referenced in python function. Is there a way how
I can I override this file in my layer. Thanks.

BR,

marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


overide glib-2.0 meson.cross.d

Marek Belisko
 

Hello,

we're using dunfell poky release and we need to bump meson from 0.53.2
to 0.55 because of cuda cross compilation issues in 0.53.2. After bump
we start seeing build problem in glib-2.0 which was fixed in poky by
commit:

85d3e045bdec5c3649c55ea334969641382d7758 - glib-2.0: correct build
with latest meson

O overtook patch to my local meta layer but this is not simply working
cos meson.cross.d is referenced in python function. Is there a way how
I can override this file in my layer. Thanks.

BR,

marek


Yocto Project Virtual Summit 2020 - CFP Open

Reyna, David
 

Hello all!
 
Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space. 
 
Organized in conjunction with ELCE 2020, this 2-day event is where individuals will learn about Yocto Project’s direction — including, but not limited to, new releases, development tools, features — get training on the next wave of embedded Linux technologies, and network with their industry peers, Yocto Project maintainers and experts.
FORMAT: The class will be presented in Zoom. It will be highly interactive with experienced teachers from around the world, and includes chat sessions, side rooms, teaching assistants, and hands-on exercises with live class accounts.
1)  Yocto Project Virtual Summit
 
DATE: Thursday, October 29 and Friday, October 30, 2020
TIME: 12.00PM-GMT to 8.00PM-GMT (5AM to 1PM in PST time, 8AM-4PM in EDT time, 5.30PM-1.30AM in India), as per ELCE
LOCATION: Zoom
COST: $40 USD
REGISTRATION: Go to the ELCE registration site and add Yocto Project Summit as part of your registration (when the extra events become available)
 
2) Yocto Project Virtual Summit - Call For Papers (CFP)
 
The CFP is now open. Become a presenter yourself and share your expertise!
CFP Closes: 11:59 PM PST on Monday, September 21, 2020
CFP Notifications: Monday, September 28, 2020
Slide Due Date: Monday, October 26, 2020
 
 
CFP list of sample topics:
  • DevTool
  • Layer quality: e.g. creating robust layers, safely using existing layers
  • Future languages (e.g. Rust)
  • Productivity tricks and tools, Best Practices
  • VS Code integration
  • Security
  • Reproducibility
  • Init systems: pros and cons, selection, configuration
  • Leveraging the new runqueue optimizations for mirrors, reproducible builds
  • Supporting the Application Developer
  • DevOps, CI/CD
  • Containers, VMs
  • Working with/creating BSPs
  • Practical use of the Yocto Project
 
Best regards,
Yocto Project Advocacy Team
 
If you have any questions or issues, contact us at: conferences@...
 
 
 
 
 
 


Yocto Project Virtual Summit 2020 - CFP Open

Reyna, David
 

Hello all!
 
Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space. 
 
Organized in conjunction with ELCE 2020, this 2-day event is where individuals will learn about Yocto Project’s direction — including, but not limited to, new releases, development tools, features — get training on the next wave of embedded Linux technologies, and network with their industry peers, Yocto Project maintainers and experts.
FORMAT: The class will be presented in Zoom. It will be highly interactive with experienced teachers from around the world, and includes chat sessions, side rooms, teaching assistants, and hands-on exercises with live class accounts.
1)  Yocto Project Virtual Summit
 
DATE: Thursday, October 29 and Friday, October 30, 2020
TIME: 12.00PM-GMT to 8.00PM-GMT (5AM to 1PM in PST time, 8AM-4PM in EDT time, 5.30PM-1.30AM in India), as per ELCE
LOCATION: Zoom
COST: $40 USD
REGISTRATION: Go to the ELCE registration site and add Yocto Project Summit as part of your registration (when the extra events become available)
 
2) Yocto Project Virtual Summit - Call For Papers (CFP)
 
The CFP is now open. Become a presenter yourself and share your expertise!
CFP Closes: 11:59 PM PST on Monday, September 21, 2020
CFP Notifications: Monday, September 28, 2020
Slide Due Date: Monday, October 26, 2020
 
 
CFP list of sample topics:
  • DevTool
  • Layer quality: e.g. creating robust layers, safely using existing layers
  • Future languages (e.g. Rust)
  • Productivity tricks and tools, Best Practices
  • VS Code integration
  • Security
  • Reproducibility
  • Init systems: pros and cons, selection, configuration
  • Leveraging the new runqueue optimizations for mirrors, reproducible builds
  • Supporting the Application Developer
  • DevOps, CI/CD
  • Containers, VMs
  • Working with/creating BSPs
  • Practical use of the Yocto Project
 
Best regards,
Yocto Project Advocacy Team
 
If you have any questions or issues, contact us at: conferences@...
 
 
 
 
 
 


Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020

Trevor Woerner
 

Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolly, Jan-Simon Möller, Alejandro H, Bruce
Ashfield, Armin Kuster, Richard Purdie, David Reyna, Steve Sakoman, Michael
Halstead, Ross Burton, Paul Barker, Mark Morton, Scott Murray, Jeremy
Puhlman, Joshua Watt, Jon Mason, Randy MacLeod

== notes ==
- entered m3 feature freeze
- working on a couple patches for 3.2
- bitbake server startup changed to avoid recently discovered issues will wait
for 3.3 to make default
- one more round of recipe upgrades before m3 build (later this week)
- -fno-common back to gcc10 default
- still some AB issues
- looking for help with unassigned bugs

== general ==
RP: list of 3.2 things:
Mark’s hash equivalency prserv fix
RP: where are we with bind?
Armin: haven’t gotten around to sending them
RP: please do so
RP: want to get more of the AUH upgrades in too.
RP: Alex has queued up the rest.
RP: high priority bitbake bug on startup that needs to go in
docs changes, we want to cut over to sphinx before m3

TrevorW: what’s the -fno-common issue?
RP: gcc changed defaults with gcc10, caused namespaces to overlap (and code
builds to fail), we temporarily switched away from the new default, waited
for upstream and created patches, now we can switch back to gcc10’s
default

Joshua: what still needs to be done with the docs?
RP: check Nico’s doc. right now: mostly marking up the code sections. please
coordinate on the mailing list

PaulB: will be giving a talk at the upcoming Linaro Connect on license
compliance with Yocto, Linaro Connect (virtual) is supposed to be free to
attend this year

RP: i’ve heard that YP was mentioned at last week’s Plumbers, does anyone
know when/where it could have been mentioned?
(various): not sure
Scott: I don’t see Khem here, maybe he was talking about it?
TrevorW: Alistair Francis is a contributor to YP and RISC-V, it could have
been brought up in relation to that. the RISC-V YP BSP carries a lot of
patches

Randy: Saul Wold is joining WR today!
RP: glad to hear he’s returning to YP


Re: RootFS Size increase during Migration

Khem Raj
 

On Thu, Sep 3, 2020 at 10:18 PM Aashik Aswin <thisisaash9698@...> wrote:

Hi Developers,

I am migrating my code from Yocto Thud (4.19) Kernel to Yocto Zeus (5.4) Kernel.

The recipes and conf files are essentially the same, but I am seeing a substantial increase in the RootFS Size and Subsequent final image size (Close to 40 MB).

Any idea on how we can debug this or where we can start for inspecting why the image size increase.
Enable buildhistory in both builds
https://www.yoctoproject.org/docs/3.1/dev-manual/dev-manual.html#enabling-and-disabling-build-history
once you have it enabled build the images (assuming you are building
in two different workspaces ) you can diff installed-package-sizes.txt
from two builds
and it should give you some hints, if you are switching the build in
same workspace between two releases then you can do two builds and
inside buildhistory
folder run git show cmd which should show you delta between last two builds

Thanks,
Aashik


RootFS Size increase during Migration

Aashik Aswin
 

Hi Developers,

I am migrating my code from Yocto Thud (4.19) Kernel to Yocto Zeus (5.4) Kernel.

The recipes and conf files are essentially the same, but I am seeing a substantial increase in the RootFS Size and Subsequent final image size (Close to 40 MB).

Any idea on how we can debug this or where we can start for inspecting why the image size increase.

Thanks,
Aashik


Error while building dahdi-linux along with Rocko Yocto #yocto #rocko #dahdi

@prashant2314
 

Hi,

I'm using Rocko yocto for my project, in this when I'm including dahdi-linux I'm getting unneeded files error.

Error logs:    

ERROR: dahdi-linux-3.1.0-r0 do_package: QA Issue: dahdi-linux: Files/directories were installed but not shipped in any package:  
  /usr/lib    
  /usr/lib/hotplug    
  /usr/lib/hotplug/firmware    
  /lib/firmware    
  /lib/firmware/dahdi-fw-te133.bin    
  /lib/firmware/dahdi-fw-tc400m.bin    
  /lib/firmware/dahdi-fw-oct6114-256.bin    
  /lib/firmware/.dahdi-fw-oct6114-032-1.05.01    
  /lib/firmware/dahdi-fw-te436.bin    
  /lib/firmware/dahdi-fw-a8b.bin    
  /lib/firmware/.dahdi-fw-tc400m-MR6.12    
  /lib/firmware/.dahdi-fw-a8a-1d0017    
  /lib/firmware/.dahdi-fw-a8b-1f001e    
  /lib/firmware/.dahdi-fw-hx8-2.06    
  /lib/firmware/dahdi-fw-te435.bin    
  /lib/firmware/dahdi-fw-hx8.bin    
  /lib/firmware/.dahdi-fw-te436-10017    
  /lib/firmware/.dahdi-fw-te820-1.76    
  /lib/firmware/dahdi-fw-te820.bin    
  /lib/firmware/dahdi-fw-te134.bin    
  /lib/firmware/dahdi-fw-a4a.bin    
  /lib/firmware/.dahdi-fw-te435-13001e    
  /lib/firmware/dahdi-fw-a8a.bin    
  /lib/firmware/dahdi-fw-oct6114-128.bin    
  /lib/firmware/.dahdi-fw-oct6114-064-1.05.01     
  /lib/firmware/dahdi-fw-oct6114-064.bin     
  /lib/firmware/.dahdi-fw-te133-7a001e    
  /lib/firmware/.dahdi-fw-vpmoct032-1.12.0     
  /lib/firmware/.dahdi-fw-a4a-a0017     
  /lib/firmware/.dahdi-fw-oct6114-128-1.05.01     
  /lib/firmware/.dahdi-fw-oct6114-256-1.05.01     
  /lib/firmware/dahdi-fw-oct6114-032.bin     
  /lib/firmware/dahdi-fw-vpmoct032.bin     
  /lib/firmware/.dahdi-fw-a4b-d001e    
  /lib/firmware/dahdi-fw-a4b.bin
  /lib/firmware/.dahdi-fw-te134-780017    

**Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.**     
dahdi-linux: 36 installed and not shipped files. [installed-vs-shipped]    
ERROR: dahdi-linux-3.1.0-r0 do_package: Fatal QA errors found, failing task.    
ERROR: dahdi-linux-3.1.0-r0 do_package: Function failed: do_package    
ERROR: Logfile of failure stored in: /home/prashant/P_DIALT/RENESAS/RZ_G2E    /Yocto_for_experiments/rzg2_bsp/build/tmp/work/ek874-poky-linux/dahdi-linux/3.1.0-r0/temp/log.do_package.9978    
ERROR: Task (/home/prashant/P_DIALT/RENESAS/RZ_G2E/Yocto_for_experiments/rzg2_bsp/build/../meta-telephony/recipes-isdn/dahdi-linux/dahdi-linux_3.1.0.bb:do_package) failed with exit code '1'    
NOTE: Tasks Summary: Attempted 4969 tasks of which 4968 didn't need to be rerun and 1 failed.  
    I've tried these method also    
    "https://www.yoctoproject.org/pipermail/yocto/2016-January/028127.html"    
    "https://stackoverflow.com/questions/49748528/yocto-files-directories-were-installed-but-not-shipped-in-any-package"  
   in **dahdi-linux_3.1.0.bb** file, then also I'm facing same issue.    
please assist me to solve this.   

Regard,    
Prashant Singh


Re: How to integrate kernel-module in yocto-dunfell? #yocto #dunfell #apt #tx2 #kernel

Marek Belisko
 

On Thu, Sep 3, 2020 at 8:56 AM <kilian.brandt@...> wrote:

Hi Khem, thanks for your reply! Now I am a bit confused. Marek has sent me another recipe:
Shared recipe should be the same as one from meta-oe :). So you can
include it in your image and it should be build then.

LICENSE = "GPLv2"

LIC_FILES_CHKSUM = "file://COPYING;md5=72d977d697c3c05830fdff00a7448931"

SRCREV = "6003f9997587e6a563cebf1f246bcd0eb6deff3d"

PV = "1.0+git${SRCPV}"



SRC_URI = "git://github.com/hartkopp/can-isotp.git;protocol=https"



S = "${WORKDIR}/git"



inherit module



EXTRA_OEMAKE += "KERNELDIR=${STAGING_KERNEL_DIR}"


Do you know if that is allready fixed for kernel 5,2+ ?

Best regards!

BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: How to integrate kernel-module in yocto-dunfell? #yocto #dunfell #apt #tx2 #kernel

kilian.brandt@...
 

Hi Khem, thanks for your reply! Now I am a bit confused. Marek has send me another recipe:

 LICENSE = "GPLv2"

LIC_FILES_CHKSUM = "file://COPYING;md5=72d977d697c3c05830fdff00a7448931"

SRCREV = "6003f9997587e6a563cebf1f246bcd0eb6deff3d"

PV = "1.0+git${SRCPV}"

 

SRC_URI = "git://github.com/hartkopp/can-isotp.git;protocol=https"

 

S = "${WORKDIR}/git"

 

inherit module

 

EXTRA_OEMAKE += "KERNELDIR=${STAGING_KERNEL_DIR}"


Do you know if that is allready fixed for kernel 5,2+ ?

Best regards!


[meta-cgl][PATCH] pacemaker: Fix build with -fno-common

Yu, Mingli
 

From: Mingli Yu <mingli.yu@...>

Starting with GCC >= 10.x, -fno-common is used as default
instead of -fcommon.

Make the function definiton extern to fix the build failure.

Set the default OCF_ROOT_DIR to $libdir/ocf to make the
resource agents components more compatible.

Signed-off-by: Mingli Yu <mingli.yu@...>
---
.../0001-Mark-declaration-with-extern.patch | 46 +++++++++++++++++++
...maker-set-OCF_ROOT_DIR-to-libdir-ocf.patch | 32 +++++++++++++
.../recipes-cgl/pacemaker/pacemaker_2.0.3.bb | 2 +
3 files changed, 80 insertions(+)
create mode 100644 meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch
create mode 100644 meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch

diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch
new file mode 100644
index 0000000..5729447
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch
@@ -0,0 +1,46 @@
+From e1abd3b7c7a0122813e4d0abdb079df10104882c Mon Sep 17 00:00:00 2001
+From: Mingli Yu <mingli.yu@...>
+Date: Thu, 3 Sep 2020 04:44:09 +0000
+Subject: [PATCH] Mark declaration with extern
+
+Fixes build with gcc 10+
+
+Upstream-Status: Pending
+
+Signed-off-by: Mingli Yu <mingli.yu@...>
+---
+ daemons/attrd/pacemaker-attrd.h | 4 ++--
+ daemons/execd/pacemaker-execd.h | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/daemons/attrd/pacemaker-attrd.h b/daemons/attrd/pacemaker-attrd.h
+index cc8e29ee1..76778915e 100644
+--- a/daemons/attrd/pacemaker-attrd.h
++++ b/daemons/attrd/pacemaker-attrd.h
+@@ -106,8 +106,8 @@ typedef struct attribute_value_s {
+ gboolean seen;
+ } attribute_value_t;
+
+-crm_cluster_t *attrd_cluster;
+-GHashTable *attributes;
++extern crm_cluster_t *attrd_cluster;
++extern GHashTable *attributes;
+
+ #define attrd_send_ack(client, id, flags) \
+ crm_ipcs_send_ack((client), (id), (flags), "ack", __FUNCTION__, __LINE__)
+diff --git a/daemons/execd/pacemaker-execd.h b/daemons/execd/pacemaker-execd.h
+index 4a52d9183..dab3ccdbe 100644
+--- a/daemons/execd/pacemaker-execd.h
++++ b/daemons/execd/pacemaker-execd.h
+@@ -20,7 +20,7 @@
+ # include <gnutls/gnutls.h>
+ # endif
+
+-GHashTable *rsc_list;
++extern GHashTable *rsc_list;
+
+ typedef struct lrmd_rsc_s {
+ char *rsc_id;
+--
+2.26.2
+
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch
new file mode 100644
index 0000000..1ff9c7d
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch
@@ -0,0 +1,32 @@
+From 3ca78a6441eefc26f18211375b18205ed6fc28c6 Mon Sep 17 00:00:00 2001
+From: Mingli Yu <mingli.yu@...>
+Date: Thu, 3 Sep 2020 05:26:36 +0000
+Subject: [PATCH] pacemaker: set OCF_ROOT_DIR to $libdir/ocf
+
+* Set the default OCF_ROOT_DIR to $libdir/ocf
+ to make the resource agents components more
+ compatible
+
+Upstream-Status: Pending
+
+Signed-off-by: Mingli Yu <mingli.yu@...>
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index 58d39cdc0..eb4275560 100644
+--- a/configure.ac
++++ b/configure.ac
+@@ -315,7 +315,7 @@ dnl This defaults to /usr/lib rather than libdir because it's determined by the
+ dnl OCF project and not pacemaker. Even if a user wants to install pacemaker to
+ dnl /usr/local or such, the OCF agents will be expected in their usual
+ dnl location. However, we do give the user the option to override it.
+-OCF_ROOT_DIR="/usr/lib/ocf"
++OCF_ROOT_DIR="$libdir/ocf"
+ AC_ARG_WITH([ocfdir],
+ [AS_HELP_STRING([--with-ocfdir=DIR],
+ [OCF resource agent root directory (advanced option: changing this may break other cluster components unless similarly configured) @<:@/usr/lib/ocf@:>@])],
+--
+2.26.2
+
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb
index 9b63acd..56f3bc4 100644
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb
@@ -16,6 +16,8 @@ DEPENDS = "corosync libxslt libxml2 gnutls resource-agents libqb python3-native"
SRC_URI = "git://github.com/ClusterLabs/${BPN}.git \
file://0006-Fix-tools-Fix-definition-of-curses_indented_printf.patch \
file://0001-Fix-python3-usage.patch \
+ file://0001-Mark-declaration-with-extern.patch \
+ file://0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch \
file://volatiles \
file://tmpfiles \
"
--
2.26.2


Re: Query on building applications and catch exceptions across different shared libraries

Khem Raj
 

On Wed, Sep 2, 2020 at 8:06 PM SIMON BABY <simonkbaby@...> wrote:

No I am not using -fexceptions compiler flag .
OK please add it to your CXXFLAGS and see if it helps.


Rgds
Simon

On Wednesday, September 2, 2020, Khem Raj <raj.khem@...> wrote:

On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@...> wrote:

Hello,

I have an issue with my throw , catch code in c++. If i throw an error after the openssl library call, my application crashes. If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe?
are you using -fexceptions to compile your application ?

regards
Simon


Re: Query on building applications and catch exceptions across different shared libraries

SIMON BABY
 

No I am not using -fexceptions compiler flag .

Rgds
Simon


On Wednesday, September 2, 2020, Khem Raj <raj.khem@...> wrote:
On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@...> wrote:
>
> Hello,
>
> I have an issue with my throw , catch code in c++.  If i throw an error after the openssl library call, my application crashes.  If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe?
>

are you using -fexceptions to compile your application ?

> regards
> Simon
>

7381 - 7400 of 57813