* Sanitycheck problem @ 2022-01-13 21:30 Mike Jones 2022-01-13 22:42 ` Patrick Williams 0 siblings, 1 reply; 6+ messages in thread From: Mike Jones @ 2022-01-13 21:30 UTC (permalink / raw) To: OpenBMC Maillist Hi, If i bitbske -c devshell dbus-sensors, them meson build, sanitycheck.exe fails with a exec for at error. Is there a workaround? The goal is to modify code and compile without bitbaking. If there is better solution, let me know. Mike Sent from my iPad ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Sanitycheck problem 2022-01-13 21:30 Sanitycheck problem Mike Jones @ 2022-01-13 22:42 ` Patrick Williams 2022-01-14 0:24 ` Mike Jones 0 siblings, 1 reply; 6+ messages in thread From: Patrick Williams @ 2022-01-13 22:42 UTC (permalink / raw) To: Mike Jones; +Cc: OpenBMC Maillist [-- Attachment #1: Type: text/plain, Size: 386 bytes --] On Thu, Jan 13, 2022 at 02:30:43PM -0700, Mike Jones wrote: > If i bitbske -c devshell dbus-sensors, them meson build, sanitycheck.exe fails with a exec for at error. What is 'sanitycheck.exe'? I don't recognize that in any way and a search on our GH repo isn't showing anything either: https://github.com/search?q=org%3Aopenbmc+sanitycheck&type=code -- Patrick Williams [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Sanitycheck problem 2022-01-13 22:42 ` Patrick Williams @ 2022-01-14 0:24 ` Mike Jones 2022-01-14 18:41 ` Patrick Williams 0 siblings, 1 reply; 6+ messages in thread From: Mike Jones @ 2022-01-14 0:24 UTC (permalink / raw) To: Patrick Williams; +Cc: OpenBMC Maillist [-- Attachment #1: Type: text/plain, Size: 2074 bytes --] 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. > On Jan 13, 2022, at 3:42 PM, Patrick Williams <patrick@stwcx.xyz> wrote: > > On Thu, Jan 13, 2022 at 02:30:43PM -0700, Mike Jones wrote: >> If i bitbske -c devshell dbus-sensors, them meson build, sanitycheck.exe fails with a exec for at error. > > What is 'sanitycheck.exe'? I don't recognize that in any way and a > search on our GH repo isn't showing anything either: > > https://github.com/search?q=org%3Aopenbmc+sanitycheck&type=code > > -- > Patrick Williams [-- Attachment #2: Type: text/html, Size: 4667 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Sanitycheck problem 2022-01-14 0:24 ` Mike Jones @ 2022-01-14 18:41 ` Patrick Williams 2022-01-17 17:17 ` Mike Jones 0 siblings, 1 reply; 6+ messages in thread From: Patrick Williams @ 2022-01-14 18:41 UTC (permalink / raw) To: Mike Jones; +Cc: OpenBMC Maillist [-- 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 --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Sanitycheck problem 2022-01-14 18:41 ` Patrick Williams @ 2022-01-17 17:17 ` Mike Jones 2022-01-17 21:24 ` Mike Jones 0 siblings, 1 reply; 6+ messages in thread From: Mike Jones @ 2022-01-17 17:17 UTC (permalink / raw) To: Patrick Williams; +Cc: OpenBMC Maillist Patrick, There is no ninja.build file, so it won’t compile. Nonetheless, in general, how are people developing, compiling, testing things like dbus_semsors? I spent some time trying to compile it on Ubuntu, and I just went down a rabbit hole. I assume yocto has some general cross compilation other than devtool? Sorry for such a newbie question. Just a pointer and a url and I’ll go do the learning. Mike Sent from my iPad > On Jan 14, 2022, at 11:41 AM, Patrick Williams <patrick@stwcx.xyz> wrote: > > 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Sanitycheck problem 2022-01-17 17:17 ` Mike Jones @ 2022-01-17 21:24 ` Mike Jones 0 siblings, 0 replies; 6+ messages in thread From: Mike Jones @ 2022-01-17 21:24 UTC (permalink / raw) To: Patrick Williams; +Cc: OpenBMC Maillist Patrick, I figured out how to build and install and sdk, and then I could compile properly. Mike Sent from my iPad > On Jan 17, 2022, at 10:17 AM, Mike Jones <proclivis@gmail.com> wrote: > > Patrick, > > There is no ninja.build file, so it won’t compile. > > Nonetheless, in general, how are people developing, compiling, testing things like dbus_semsors? I spent some time trying to compile it on Ubuntu, and I just went down a rabbit hole. I assume yocto has some general cross compilation other than devtool? > > Sorry for such a newbie question. Just a pointer and a url and I’ll go do the learning. > > Mike > > Sent from my iPad > >>> On Jan 14, 2022, at 11:41 AM, Patrick Williams <patrick@stwcx.xyz> wrote: >>> >>> 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-01-17 21:25 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2022-01-17 17:17 ` Mike Jones 2022-01-17 21:24 ` Mike Jones
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.