[yocto] Build break in the latest openbmc tree.

Khem Raj raj.khem at gmail.com
Wed Sep 4 11:01:29 AEST 2019



On 9/3/19 5:36 PM, Brad Bishop wrote:
> at 5:16 PM, Jae Hyun Yoo <jae.hyun.yoo at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 2334 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190903/26d8ca03/attachment.key>


More information about the openbmc mailing list