Sanitycheck problem

[Patrick Williams]

On Thu, Jan 13, 2022 at 05:24:00PM -0700, Mike Jones wrote:
> This is the error:
> 
> root at ubuntu:~/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git# <mailto:root at ubuntu:~/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git#> meson build
> The Meson build system
> Version: 0.58.1
> Source dir: /home/openbmc/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git
> Build dir: /home/openbmc/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git/build
> Build type: native build
> Project name: dbus-sensors
> Project version: 0.1
>  
> meson.build:1:0: ERROR: Could not invoke sanity test executable: [Errno 8] Exec format error: '/home/openbmc/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git/build/meson-private/sanitycheckcpp.exe'.
>  
> A full log can be found at /home/openbmc/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-rroot at ubuntu:~root at ubrootroot@ubuntu:~/share/design/code/openbmc/build/ast2600-default/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/dbus-sensors/0.1+gitAUTOINC+26601e8919-r0/git#
> 
> The path to sanitycheckcpp.exe is there, but fails, as if it must run on a different architecture.

I'm not sure what is going on and I don't really use devtool very often.  The
"Build type: native build" is where things are going wrong though.  You've tried
to get bitbake to set you up a cross-compile environment (targeting ARM) and
yet meson thinks you're building a native (targeting x86 likely).  Usually
bitbake has some special environment settings or a cross-env file for Meson, so
however you're invoking meson might be missing that.

Is it actually necessary to call meson anyhow?  Hasn't the 'configure' step
already ran when devtool sets up the environment?  `meson build` says "set up
a new meson directory named build".  Did you intend something like
`ninja -C build`?

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220114/a93bde0c/attachment-0001.sig>