[yocto] Error at extensible sdk installation

[Markus Volk]

Hello,

i built myself an extensible sdk from current master branch. After successful 
build i tried to install and got the following error:

/home/builder/tuxbox_sdk/tmp/sysroots/x86_64/usr/bin/postinst-docbook-xsl-stylesheets-native-xmlcatalog:
 line 5: xmlcatalog: command not found

and was able to fix it wby adding "xmlcatalog" to HOSTTOOLS, but i guess thats 
not the propper way to fix it
 
-- 
Markus Volk 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] WARNING: bluez5-5.50-r0 do_fetch: Failed to fetch URL file://variscite-bt.conf

[Zoran Stojsavljevic]

No any time for the investigation..

Here is the workaround. The file variscite-bt.conf (content is here):
https://github.com/ZoranStojsavljevic/imx6-sabre-automotive-bsp/blob/master/Issues/variscite-bt.conf

I inserted in one of the paths searched by fetcher, which are given here:
https://github.com/ZoranStojsavljevic/imx6-sabre-automotive-bsp/blob/master/Issues/Fetch_failed.log

This solved my problem (again, just sticks and ropes workaround, NOT
at all final solution).

Zoran
___

On Mon, Sep 2, 2019 at 5:04 PM Ross Burton  wrote:
>
> That file isn't part of oe-core, given the name you should ask the
> variscite-bsp-platform maintainers.
>
> Ross
>
> On 27/08/2019 06:51, Zoran Stojsavljevic wrote:
> > BTW, I have created the complete description of this problem!
> > https://github.com/ZoranStojsavljevic/imx6-sabre-automotive-bsp/tree/master/Issues
> >
> > Best Regards,
> > Zoran
> > ___
> >
> > On Mon, Aug 26, 2019 at 5:23 PM Zoran Stojsavljevic
> > mailto:zoran.stojsavlje...@gmail.com>>
> > wrote:
> >
> > Hello Folks,
> >
> > While doing the following YOCTO build:
> > 
> > http://variwiki.com/index.php?title=Yocto_Build_Release&release=RELEASE_MORTY_V1
> >
> > Actually, using the latest available tag:
> > thud-fslc-4.14.78-mx6ul-v1.1
> > 
> > 
> >  From https://github.com/varigit/variscite-bsp-platform/tags
> >
> > I've got the following error, while compiling for both:
> > bitbake -k fsl-image-gui
> > bitbake -k fsl-image-qt5
> >
> > Seems, that the local file: file://variscite-bt.conf is somehow
> > missing?!
> >
> > I can add this file artificially, but, the question is: why this
> > file is missing???
> > ___
> >
> > Transcript follows:
> > bluez5-5.50-r0 do_fetch: Failed to fetch variscite-bt.conf
> > https://pastebin.com/U9LRtNwr
> >
> > Thank you,
> > Zoran
> > ___
> >
> >
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error at extensible sdk installation

[Khem Raj]

On Tue, Sep 3, 2019 at 12:05 AM Markus Volk  wrote:
>
>
> Hello,
>
> i built myself an extensible sdk from current master branch. After successful 
> build i tried to install and got the following error:
>
> /home/builder/tuxbox_sdk/tmp/sysroots/x86_64/usr/bin/postinst-docbook-xsl-stylesheets-native-xmlcatalog:
>  line 5: xmlcatalog: command not found
>
> and was able to fix it wby adding "xmlcatalog" to HOSTTOOLS, but i guess 
> thats not the propper way to fix it
>

infact that might be right soluition. Can you submit a patch
> --
> Markus Volk 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Error at extensible sdk installation

[Markus Volk]

On Tue, 3 Sep 2019 09:13:03 -0700
Khem Raj  wrote:

> On Tue, Sep 3, 2019 at 12:05 AM Markus Volk  wrote:
> >
> >
> > Hello,
> >
> > i built myself an extensible sdk from current master branch. After 
> > successful build i tried to install and got the following error:
> >
> > /home/builder/tuxbox_sdk/tmp/sysroots/x86_64/usr/bin/postinst-docbook-xsl-stylesheets-native-xmlcatalog:
> >  line 5: xmlcatalog: command not found
> >
> > and was able to fix it wby adding "xmlcatalog" to HOSTTOOLS, but i guess 
> > thats not the propper way to fix it
> >
> 
> infact that might be right soluition. Can you submit a patch
> > --
> > Markus Volk 
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto

Sure. Hopefully bitbake.conf is the right place to do so
-- 
Markus Volk 



0001-bitbake.conf-add-xmlcatalog-to-HOSTTOOLS.patch
Description: Binary data
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] Confusion about U-Boot setup

[Greg Wilson-Lindberg]

I've configured a sumo build, by way of QT's boot2qt to use u-boot and I am 
seeing a u-boot prompt for keypress to drop out of automatic booting on 
startup, but I don't see any configuration scripts for u-boot (uEnv.txt or a 
script) on the image or in the build tmp/ dir.

For the raspberry pi, how is u-boot configured on startup?

Regards,
Greg Wilson-Lindberg  
 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-cloud-services][PATCH] glusterfs: support usrmerge

[Bruce Ashfield]

merged

Bruce

On Fri, Aug 30, 2019 at 2:13 AM  wrote:
>
> From: Changqing Li 
>
> Signed-off-by: Changqing Li 
> ---
>  recipes-extended/glusterfs/glusterfs.inc | 8 +---
>  1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-extended/glusterfs/glusterfs.inc 
> b/recipes-extended/glusterfs/glusterfs.inc
> index 40a3922..66e2bf1 100644
> --- a/recipes-extended/glusterfs/glusterfs.inc
> +++ b/recipes-extended/glusterfs/glusterfs.inc
> @@ -64,9 +64,11 @@ do_install_append() {
>  install -m 0755 ${WORKDIR}/glusterd.init \
>  ${D}${sysconfdir}/init.d/glusterd
>
> -# Mount looks for mount.* plug-ins in /sbin; fix it with a symlink.
> -mkdir -p ${D}${base_sbindir}
> -(cd ${D}${base_sbindir}; ln -s ..${sbindir}/mount.glusterfs .)
> +if ! 
> ${@bb.utils.contains('DISTRO_FEATURES','usrmerge','true','false',d)}; then
> +# Mount looks for mount.* plug-ins in /sbin; fix it with a symlink.
> +mkdir -p ${D}${base_sbindir}
> +(cd ${D}${base_sbindir}; ln -s ..${sbindir}/mount.glusterfs .)
> +fi
>
>  # These are plug-ins, so they don't need libtool configs.
>  find ${D}${libdir}/glusterfs/${PV} -name '*.la' -exec rm -f '{}' ';'
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW36’19

[Richard Purdie]

Current Dev Position: YP 2.8 M4 Feature FreezeNext Deadline: YP 3.0
Final Release 25th Oct
SWAT Team Rotation:SWAT lead is currently: ArminSWAT team rotation:
Armin -> Paul on Sept. 6, 2019SWAT team rotation: Paul -> Ross on Sept.
13, 2019
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Next Team Meetings:Bug Triage meeting Thursday Sept 5th at 7:30am PDT (
https://zoom.us/j/454367603)Monthly Project Meeting Tuesday Sept. 3rd
at 8am PDT (https://zoom.us/j/990892712) Twitch - Next event is Tuesday
Sept. 10th at 8am PDT (https://www.twitch.tv/yocto_project)
Key Status/Updates:We’re now in feature freeze for 3.0 and working on
bug fixing for final releaseSeveral key 3.0 changes have now merged:5.2
linux-libc-kernel-headers5.2 kernel recipesRemoval of LSB and poky-lsb
and replacement with alt config testingPatches have significantly
reduced the dependency on python2Reproducible builds are now being
tested for core-image-minimalThere are the following changes still
under discussion/testing:Systemd vs. sysvinit defaults (maybe for the
poky alternative configuration tests)Making 5.2 the default kernel for
qemu (has regressions, see below)Hashserv performance issue
resolutionFinal configuration of hash equivalencytoolchain testsuite
patch seriesThe sstate hash equivalency continues to have challenges:we
need to rework the client/server communication to scale to the
autobuilderthere are some bugs in the code the autobuilder continues to
exposewe have cases where its not 100% clear what the correct behaviour
should betest cases are proving to be problematic to write in a
maintainable wayPatch merging is roughly up to date againWe have
several significant problematic bugs that are being worked on:5.2 stap
build issue on qemuarm5.2 kprobes error message (qemuarm64,
qemumips64)qemumips machine hangIf anyone has any status items for the
project they’d like to add to the weekly reports, please email
Richard+Stephen.
Planned Releases for YP 3.0 {2.8}:M3 Release 6th SeptM4 Cutoff 30th
Sept - this will be YP 3.0.YP 3.0 {2.8 (M4)} Final Release 25th Oct
Planned upcoming dot releases:YP 2.7.2 (Warrior) is planned for after
YP 3.0 release.YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.
Tracking Metrics:WDD 2413 (last week 2485) (
https://wiki.yoctoproject.org/charts/combo.html)Poky Patch
Metrics  Total patches found: 1470 (last week 1474)Patches in the
Pending State: 611 (42%) [last week 613 (41%)]
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Statushttps://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedulehttps://wiki.yoctoproject.org/wiki/Yocto_2.8_Features
The Yocto Project’s technical governance is through its Technical
Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build break in the latest openbmc tree.

[Brad Bishop]

at 5:16 PM, Jae Hyun Yoo  wrote:


On 8/27/2019 5:00 PM, Brad Bishop wrote:

On Sun, 2019-08-25 at 10:49 -0700, akuster808 wrote:

the meta-security layer should be fix now.

please update and let me know if not.

Thanks Armin!
Jae, I've pulled this into OpenBMC.  Can you give it a try?


Thanks Armin, Brad!

I tried it using the latest tree and checked that the build breakage has
gone, but a new issue happened while it's building 'qemu-native'.

| ERROR: Execution of  
'/home/yoojae/workspace/openbmc/build/tmp/work/x86_64-linux/qemu-native/4.1.0-r0/temp/run.do_configure.2396'  
failed with exit code 1:

| ERROR: unknown option --disable-libssh

So I made a patch to fix the new issue.

--- a/poky/meta/recipes-devtools/qemu/qemu.inc
+++ b/poky/meta/recipes-devtools/qemu/qemu.inc
@@ -137,7 +137,7 @@ PACKAGECONFIG[curses] =  
"--enable-curses,--disable-curses,ncurses,"

 PACKAGECONFIG[gtk+] = "--enable-gtk,--disable-gtk,gtk+3 gettext-native"
 PACKAGECONFIG[vte] = "--enable-vte,--disable-vte,vte gettext-native"
 PACKAGECONFIG[libcap-ng] = "--enable-cap-ng,--disable-cap-ng,libcap-ng,"
-PACKAGECONFIG[ssh] = "--enable-libssh,--disable-libssh,libssh,"
+PACKAGECONFIG[ssh] = "--enable-libssh2,--disable-libssh2,libssh2,"
 PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt,"
 PACKAGECONFIG[nettle] = "--enable-nettle,--disable-nettle,nettle"
 PACKAGECONFIG[libusb] = "--enable-libusb,--disable-libusb,libusb1"

Brad,
Please apply this change into the qemu recipe.


Hi Jae

Please send your patch to OE-Core.

FWIW I am able to build qemu-native without issue with OpenBMC 93ee980ed9  
although I am not using meta-security.


thx - brad
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build break in the latest openbmc tree.

[Khem Raj]

On 9/3/19 5:36 PM, Brad Bishop wrote:
> at 5:16 PM, Jae Hyun Yoo  wrote:
> 
>> On 8/27/2019 5:00 PM, Brad Bishop wrote:
>>> On Sun, 2019-08-25 at 10:49 -0700, akuster808 wrote:
 the meta-security layer should be fix now.

 please update and let me know if not.
>>> Thanks Armin!
>>> Jae, I've pulled this into OpenBMC.  Can you give it a try?
>>
>> Thanks Armin, Brad!
>>
>> I tried it using the latest tree and checked that the build breakage has
>> gone, but a new issue happened while it's building 'qemu-native'.
>>
>> | ERROR: Execution of
>> '/home/yoojae/workspace/openbmc/build/tmp/work/x86_64-linux/qemu-native/4.1.0-r0/temp/run.do_configure.2396'
>> failed with exit code 1:
>> | ERROR: unknown option --disable-libssh
>>
>> So I made a patch to fix the new issue.
>>
>> --- a/poky/meta/recipes-devtools/qemu/qemu.inc
>> +++ b/poky/meta/recipes-devtools/qemu/qemu.inc
>> @@ -137,7 +137,7 @@ PACKAGECONFIG[curses] =
>> "--enable-curses,--disable-curses,ncurses,"
>>  PACKAGECONFIG[gtk+] = "--enable-gtk,--disable-gtk,gtk+3 gettext-native"
>>  PACKAGECONFIG[vte] = "--enable-vte,--disable-vte,vte gettext-native"
>>  PACKAGECONFIG[libcap-ng] = "--enable-cap-ng,--disable-cap-ng,libcap-ng,"
>> -PACKAGECONFIG[ssh] = "--enable-libssh,--disable-libssh,libssh,"
>> +PACKAGECONFIG[ssh] = "--enable-libssh2,--disable-libssh2,libssh2,"
>>  PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt,"
>>  PACKAGECONFIG[nettle] = "--enable-nettle,--disable-nettle,nettle"
>>  PACKAGECONFIG[libusb] = "--enable-libusb,--disable-libusb,libusb1"
>>
>> Brad,
>> Please apply this change into the qemu recipe.
> 

this was intentionally introduced in [1] although commit message did not
mention about it so it could be unintended change, so I wonder if there
is something more going on, is this packageconfig edited by some other
bbappends from other layers in your setup


> Hi Jae
> 
> Please send your patch to OE-Core.
> 
> FWIW I am able to build qemu-native without issue with OpenBMC
> 93ee980ed9 although I am not using meta-security.
> 
> thx - brad

[1]
https://git.openembedded.org/openembedded-core/commit/?id=50a7dec95618080962e56fd347f505e691b7ad6f


pEpkey.asc
Description: application/pgp-keys
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 1/2] openscap: Drop nostamp

[Armin Kuster]

add cleandir depends to do_install task

This nostamp is causing issues with the yocto-check-layer when checking
hash changes.

Signed-off-by: Armin Kuster 
---
 .../recipes-openscap/openscap/openscap.inc   | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap.inc 
b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
index ed8d8ff..afa576a 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap.inc
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
@@ -40,15 +40,14 @@ do_configure_append_class-native () {
 sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${B}/config.h
 }
 
-do_clean[cleandirs] += "${STAGING_OSCAP_BUILDDIR}"
-do_install[nostamp] = "1"
-
+do_install_class-native[cleandirs] += " ${STAGING_OSCAP_BUILDDIR}"
 do_install_append_class-native () {
 oscapdir=${STAGING_OSCAP_BUILDDIR}/${datadir_native}
 install -d $oscapdir
 cp -a ${D}/${STAGING_DATADIR_NATIVE}/openscap $oscapdir
 }
 
+
 FILES_${PN} += "${PYTHON_SITEPACKAGES_DIR}"
 
 RDEPENDS_${PN} += "libxml2 python3-core libgcc bash"
-- 
2.17.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 2/2] scap-security-guide: add depends on openscap-native do_install

[Armin Kuster]

This ensures openscap-native does install the needed patches
security guilde needs to build

Minor recipe cleanup too

Signed-off-by: Armin Kuster 
---
 .../scap-security-guide/scap-security-guide.inc| 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
index 341721a..3212310 100644
--- 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
+++ 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
@@ -7,14 +7,11 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=97662e4486d9a1d09f358851d9f41a1a"
 LICENSE = "LGPL-2.1"
 
 DEPENDS = "openscap-native python3 python3-pyyaml-native python3-jinja2-native 
libxml2-native"
-RDEPENDS_${PN} = "openscap"
 
 S = "${WORKDIR}/git"
 
 inherit cmake pkgconfig python3native
 
-#PARALLEL_MAKE = ""
-
 STAGING_OSCAP_BUILDDIR = "${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
 
 OECMAKE_GENERATOR = "Unix Makefiles"
@@ -23,9 +20,13 @@ EXTRA_OECMAKE += "-DENABLE_PYTHON_COVERAGE=OFF"
 
 B = "${S}/build"
 
+do_configure[depends] += "openscap-native:do_install"
+
 do_configure_prepend () {
 sed -i -e 's:NAMES\ sed:NAMES\ ${HOSTTOOLS_DIR}/sed:g' ${S}/CMakeLists.txt
 sed -i -e 's:NAMES\ grep:NAMES\ ${HOSTTOOLS_DIR}/grep:g' 
${S}/CMakeLists.txt
 }
 
 FILES_${PN} += "${datadir}/xml"
+
+RDEPENDS_${PN} = "openscap"
-- 
2.17.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build break in the latest openbmc tree.

[Alistair Francis]

> -Original Message-
> From: Khem Raj 
> Sent: Tuesday, 3 September 2019 6:01 PM
> To: Brad Bishop ; Jae Hyun Yoo
> ; Alistair Francis 
> Cc: yocto@yoctoproject.org; OpenBMC Maillist ;
> akuster808 ; James Feist
> 
> Subject: Re: [yocto] Build break in the latest openbmc tree.
> 
> 
> 
> On 9/3/19 5:36 PM, Brad Bishop wrote:
> > at 5:16 PM, Jae Hyun Yoo  wrote:
> >
> >> On 8/27/2019 5:00 PM, Brad Bishop wrote:
> >>> On Sun, 2019-08-25 at 10:49 -0700, akuster808 wrote:
>  the meta-security layer should be fix now.
> 
>  please update and let me know if not.
> >>> Thanks Armin!
> >>> Jae, I've pulled this into OpenBMC.  Can you give it a try?
> >>
> >> Thanks Armin, Brad!
> >>
> >> I tried it using the latest tree and checked that the build breakage
> >> has gone, but a new issue happened while it's building 'qemu-native'.
> >>
> >> | ERROR: Execution of
> >> '/home/yoojae/workspace/openbmc/build/tmp/work/x86_64-
> linux/qemu-native/4.1.0-r0/temp/run.do_configure.2396'
> >> failed with exit code 1:
> >> | ERROR: unknown option --disable-libssh
> >>
> >> So I made a patch to fix the new issue.
> >>
> >> --- a/poky/meta/recipes-devtools/qemu/qemu.inc
> >> +++ b/poky/meta/recipes-devtools/qemu/qemu.inc
> >> @@ -137,7 +137,7 @@ PACKAGECONFIG[curses] =
> >> "--enable-curses,--disable-curses,ncurses,"
> >>  PACKAGECONFIG[gtk+] = "--enable-gtk,--disable-gtk,gtk+3 gettext-native"
> >>  PACKAGECONFIG[vte] = "--enable-vte,--disable-vte,vte gettext-native"
> >>  PACKAGECONFIG[libcap-ng] = "--enable-cap-ng,--disable-cap-ng,libcap-
> ng,"
> >> -PACKAGECONFIG[ssh] = "--enable-libssh,--disable-libssh,libssh,"
> >> +PACKAGECONFIG[ssh] = "--enable-libssh2,--disable-libssh2,libssh2,"
> >>  PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt,"
> >>  PACKAGECONFIG[nettle] = "--enable-nettle,--disable-nettle,nettle"
> >>  PACKAGECONFIG[libusb] = "--enable-libusb,--disable-libusb,libusb1"
> >>
> >> Brad,
> >> Please apply this change into the qemu recipe.
> >
> 
> this was intentionally introduced in [1] although commit message did not
> mention about it so it could be unintended change, so I wonder if there is
> something more going on, is this packageconfig edited by some other
> bbappends from other layers in your setup
> 

It was intentional as QEMU now uses libssh2. Sorry that I didn't mention it in 
the commit message.

Alistair

> 
> > Hi Jae
> >
> > Please send your patch to OE-Core.
> >
> > FWIW I am able to build qemu-native without issue with OpenBMC
> > 93ee980ed9 although I am not using meta-security.
> >
> > thx - brad
> 
> [1]
> https://git.openembedded.org/openembedded-
> core/commit/?id=50a7dec95618080962e56fd347f505e691b7ad6f
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto