Re: Build break in the latest openbmc tree.

Re: Build break in the latest openbmc tree.

[James Feist]

On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
> Hi brad,

+ The mailing list

> 
> 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

Re: Build break in the latest openbmc tree.

[Brad Bishop]

at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:

> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>> Hi brad,
>
> + The mailing list
>
>> 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

Re: Build break in the latest openbmc tree.

[Brad Bishop]

at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:

> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>> Hi brad,
>
> + The mailing list
>
>> 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

Re: Build break in the latest openbmc tree.

[akuster808]

On 8/22/19 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
>
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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.
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.
>
> 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
>
> thx!
> brad

Re: Build break in the latest openbmc tree.

[akuster808]

On 8/22/19 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
>
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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.
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.
>
> 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
>
> thx!
> brad

Re: Build break in the latest openbmc tree.

[Jae Hyun Yoo]

On 8/22/2019 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
> 
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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 Brad,

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

Thanks,
Jae

> Hi Armin
> 
> Could you suggest what the right thing to do here might be?
> 
> thx!
> brad
> 

Re: Build break in the latest openbmc tree.

[Jae Hyun Yoo]

On 8/22/2019 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
> 
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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 Brad,

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

Thanks,
Jae

> Hi Armin
> 
> Could you suggest what the right thing to do here might be?
> 
> thx!
> brad
> 

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

[akuster808]

the meta-security layer should be fix now.

please update and let me know if not.

-armin

On 8/22/19 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
>
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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

Re: Build break in the latest openbmc tree.

[akuster808]

the meta-security layer should be fix now.

please update and let me know if not.

-armin

On 8/22/19 6:09 PM, Brad Bishop wrote:
> at 6:38 PM, James Feist <james.feist@linux.intel.com> wrote:
>
>> On 8/22/19 3:35 PM, Jae Hyun Yoo wrote:
>>> Hi brad,
>>
>> + The mailing list
>>
>>> 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

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

[Brad Bishop]

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

Re: Build break in the latest openbmc tree.

[Brad Bishop]

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

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

[Jae Hyun Yoo]

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.

Thanks,
Jae

Re: Build break in the latest openbmc tree.

[Jae Hyun Yoo]

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.

Thanks,
Jae

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

[Brad Bishop]

at 5:16 PM, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> 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

Re: Build break in the latest openbmc tree.

[Brad Bishop]

at 5:16 PM, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> 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

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

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]



On 9/3/19 5:36 PM, Brad Bishop wrote:
> at 5:16 PM, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> 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

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2373 bytes --]

Re: Build break in the latest openbmc tree.

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]



On 9/3/19 5:36 PM, Brad Bishop wrote:
> at 5:16 PM, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> 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

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2373 bytes --]

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

[Alistair Francis]

> -----Original Message-----
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Tuesday, 3 September 2019 6:01 PM
> To: Brad Bishop <bradleyb@fuzziesquirrel.com>; Jae Hyun Yoo
> <jae.hyun.yoo@linux.intel.com>; Alistair Francis <Alistair.Francis@wdc.com>
> Cc: yocto@yoctoproject.org; OpenBMC Maillist <openbmc@lists.ozlabs.org>;
> akuster808 <akuster808@gmail.com>; James Feist
> <james.feist@linux.intel.com>
> 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 <jae.hyun.yoo@linux.intel.com> 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

Re: Build break in the latest openbmc tree.

[Alistair Francis]

> -----Original Message-----
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Tuesday, 3 September 2019 6:01 PM
> To: Brad Bishop <bradleyb@fuzziesquirrel.com>; Jae Hyun Yoo
> <jae.hyun.yoo@linux.intel.com>; Alistair Francis <Alistair.Francis@wdc.com>
> Cc: yocto@yoctoproject.org; OpenBMC Maillist <openbmc@lists.ozlabs.org>;
> akuster808 <akuster808@gmail.com>; James Feist
> <james.feist@linux.intel.com>
> 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 <jae.hyun.yoo@linux.intel.com> 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