Skip to contentSkip to conversation

Build break in the latest openbmc tree.

DISCUSSION James Feist 6 participants 10 messages Aug 22, 2019 – Sep 4, 2019 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 1 line · Jae Hyun Yoo

Hi brad,

+ The mailing list

Quoted 12 lines

We met a build break while making Intel platform builds.

ERROR: No recipes available for:

/home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend

It was added by the subtree update patch but there is no main recipe for it. Did we miss something?

Thanks,
Jae

#2 lore raw
Quoted 10 lines · James Feist
Quoted 1 line · Jae Hyun Yoo

Hi brad,

+ The mailing list

Quoted 5 lines

We met a build break while making Intel platform builds.
ERROR: No recipes available for:
/home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend It was added by the subtree update patch but there is no main recipe for it. Did we miss something? Thanks,
Jae

Hi Jae

linux-stable is in meta-odroid:
https://lists.yoctoproject.org/pipermail/yocto/2019-August/046424.html

It isn’t clear to me if meta-security is supposed to have a hard dependency on meta-odroid or not.

Hi Armin

Could you suggest what the right thing to do here might be?

thx!
brad

#3 lore raw
Quoted 15 lines · Brad Bishop
Quoted 12 lines · James Feist
Quoted 1 line · Jae Hyun Yoo

Hi brad,

+ The mailing list

Quoted 7 lines

We met a build break while making Intel platform builds.
ERROR: No recipes available for:
/home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend It was added by the subtree update patch but there is no main recipe
for it. Did we miss something?
Thanks,
Jae

Quoted 7 lines

Hi Jae

linux-stable is in meta-odroid:
https://lists.yoctoproject.org/pipermail/yocto/2019-August/046424.html

It isn’t clear to me if meta-security is supposed to have a hard dependency on meta-odroid or not.

It should not. The is bad behavior and I wanted to avoid such an issue. meta-security is a s/w layer and should be BSP neutral.  I did not achieve that.

Quoted 4 lines

Hi Armin

Could you suggest what the right thing to do here might be?

Yeah, i believe the recipe in meta-security should be linux-%.* . My testing unfortunately kept the meta-odroid layer included so its a false positive. Not my intent . I know the qemu machines should build clean with any changes in that layer.

I am testing changes now to correct his issue.

- armin

Quoted 3 lines

thx!
brad

#4 lore raw
In reply to Brad Bishop
Quoted 13 lines · Brad Bishop
Quoted 10 lines · James Feist
Quoted 1 line · Jae Hyun Yoo

Hi brad,

+ The mailing list

Quoted 5 lines

We met a build break while making Intel platform builds.
ERROR: No recipes available for:
/home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend It was added by the subtree update patch but there is no main recipe for it. Did we miss something? Thanks,
Jae

Quoted 6 lines

Hi Jae

linux-stable is in meta-odroid:
https://lists.yoctoproject.org/pipermail/yocto/2019-August/046424.html

It isn’t clear to me if meta-security is supposed to have a hard dependency on meta-odroid or not.

Hi Brad,

I checked that 'meta-odroid' isn't in OpenBMC tree. Should we add it into our openembedded layer?

Thanks,
Jae

Quoted 7 lines

Hi Armin

Could you suggest what the right thing to do here might be?

thx!
brad

#5 lore raw
In reply to Brad Bishop

the meta-security layer should be fix now.

please update and let me know if not.

-armin

Quoted 29 lines · Brad Bishop
Quoted 12 lines · James Feist
Quoted 1 line · Jae Hyun Yoo

Hi brad,

+ The mailing list

Quoted 7 lines

We met a build break while making Intel platform builds.
ERROR: No recipes available for:
/home/yoojae/workspace/openbmc/meta-security/recipes-kernel/linux/linux-stable_5.2.bbappend It was added by the subtree update patch but there is no main recipe
for it. Did we miss something?
Thanks,
Jae

Hi Jae

linux-stable is in meta-odroid:
https://lists.yoctoproject.org/pipermail/yocto/2019-August/046424.html

It isn’t clear to me if meta-security is supposed to have a hard dependency on meta-odroid or not.

Hi Armin

Could you suggest what the right thing to do here might be?

thx!
brad

#6 lore raw
Quoted 3 lines · 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?

-brad

#7 lore raw
Quoted 9 lines · Brad Bishop
Quoted 3 lines · 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.

poky/meta/recipes-devtools/qemu/qemu.inc +1 -1
@@ -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.

Thanks,
Jae

#8 lore raw
Quoted 31 lines · Jae Hyun Yoo
Quoted 6 lines · Brad Bishop
Quoted 3 lines · 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.

poky/meta/recipes-devtools/qemu/qemu.inc +0 -0
@@ -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,"

poky/meta/recipes-devtools/qemu/qemu.inc +1 -1
-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"
Quoted 2 lines

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

#9 lore raw
Quoted 35 lines · Brad Bishop
Quoted 33 lines · Jae Hyun Yoo
Quoted 6 lines · Brad Bishop
Quoted 3 lines · 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.

poky/meta/recipes-devtools/qemu/qemu.inc +0 -0
@@ -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,"

poky/meta/recipes-devtools/qemu/qemu.inc +1 -1
-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"

Quoted 3 lines
Quoted 2 lines

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

Quoted 8 lines

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

#10 lore raw
Quoted 50 lines

-----Original Message-----
From: Khem Raj <[email protected]>
Sent: Tuesday, 3 September 2019 6:01 PM
To: Brad Bishop <[email protected]>; Jae Hyun Yoo <[email protected]>; Alistair Francis <[email protected]>
Cc: [email protected]; OpenBMC Maillist <[email protected]>; akuster808 <[email protected]>; James Feist <[email protected]>
Subject: Re: [yocto] Build break in the latest openbmc tree.

Quoted 10 lines · Brad Bishop
Quoted 8 lines · Jae Hyun Yoo
Quoted 6 lines · Brad Bishop
Quoted 3 lines · 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?

Quoted 7 lines
Quoted 7 lines

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'

Quoted 5 lines
Quoted 5 lines

failed with exit code 1:
| ERROR: unknown option --disable-libssh

So I made a patch to fix the new issue.

Quoted 7 lines
Quoted 7 lines
poky/meta/recipes-devtools/qemu/qemu.inc +0 -0
@@ -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,"

Quoted 6 lines
Quoted 6 lines
poky/meta/recipes-devtools/qemu/qemu.inc +1 -1
-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"

Quoted 9 lines
Quoted 3 lines
Quoted 2 lines

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

Quoted 13 lines
Quoted 9 lines

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