All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Mike Jones <proclivis@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Sanitycheck problem
Date: Fri, 14 Jan 2022 12:41:05 -0600	[thread overview]
Message-ID: <YeHDwS7/D9JY4XXw@heinlein> (raw)
In-Reply-To: <47171FDF-05E4-4501-A499-137A09D2FCCB@gmail.com>

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

On Thu, Jan 13, 2022 at 05:24:00PM -0700, Mike Jones wrote:
> This is the error:
> 
> root@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@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@ubuntu:~root@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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-14 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 21:30 Sanitycheck problem Mike Jones
2022-01-13 22:42 ` Patrick Williams
2022-01-14  0:24   ` Mike Jones
2022-01-14 18:41     ` Patrick Williams [this message]
2022-01-17 17:17       ` Mike Jones
2022-01-17 21:24         ` Mike Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YeHDwS7/D9JY4XXw@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    --cc=proclivis@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.