From: "Theodore A. Roth" <troth@openavr.org>
To: meta-virtualization@lists.yoctoproject.org
Subject: Problems building podman and buildah
Date: Wed, 8 Nov 2023 16:41:47 -0700 [thread overview]
Message-ID: <CAFMvBt3aumWLd7vzsUHEZ5TvxDkC_2Tjfa=NJVe3qkkJxYieLg@mail.gmail.com> (raw)
Hi,
With the recent updates to meta-virtualization master branch for
podman (to 4.7.1) and buildah (to 1.32.0),
our builds are breaking.
I'm seeing the problem when building for either raspberrypi4 or qemuarm64.
The podman failure appears to be due to not using the native go-md2man
binary when building the man pages.
I was able to work around this by adding the following to the
do_compile() and do_install() functions
in the podman recipe:
export GOMD2MAN="${RECIPE_SYSROOT_NATIVE}/usr/bin/go-md2man"
I'm more than happy to send a patch if that is the correct fix.
I'm stumped on the buildah failure. Here's the error messages:
NOTE: Executing Tasks
ERROR: buildah-1.32.0-r0 do_package_qa: QA Issue: Architecture did not
match (x86-64, expected ARM) in
/usr/lib/go/src/github.com/containers/buildah/internal/mkcw/embed/entrypoint
[arch]
ERROR: buildah-1.32.0-r0 do_package_qa: Fatal QA errors were found,
failing task.
ERROR: Logfile of failure stored in:
/home/troth/work/bedrock/bedrock-main/build-rpi4/tmp/work/cortexa7t2hf-neon-vfpv4-trimble-linux-gnueabi/buildah/1.32.0/temp/log.do_package_qa.1252786
ERROR: Task (/home/troth/work/bedrock/bedrock-main/build-rpi4/../oe/meta-virtualization/recipes-containers/buildah/buildah_git.bb:do_package_qa)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 5377 tasks of which 5353 didn't need to
be rerun and 1 failed.
Summary: 1 task failed:
/home/troth/work/bedrock/bedrock-main/build-rpi4/../oe/meta-virtualization/recipes-containers/buildah/buildah_git.bb:do_package_qa
Summary: There were 2 ERROR messages, returning a non-zero exit code.
This looks like bitbake is not using the go cross compiler to build
the buildah binaries.
Since I'm not versed in go development, I don't know how to fix or
work around this one.
Looking over the recipe and comparing it to other recipes did not
yield any obvious change that I could try.
Curious if anyone else is seeing either of these issues to allow me to
determine if this is specific to my setup or a general problem with
meta-virtualization.
I'm building all of this using the master branches of poky,
meta-openembedded, meta-raspberrypi and meta-virtualization (all
updated from upstream git servers today).
Can provide any other information if needed.
Ted Roth
next reply other threads:[~2023-11-08 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 23:41 Theodore A. Roth [this message]
2023-11-09 1:56 ` [meta-virtualization] Problems building podman and buildah Bruce Ashfield
[not found] ` <1795D1B2F2566CE7.15940@lists.yoctoproject.org>
2023-11-09 6:28 ` Bruce Ashfield
2023-11-09 13:48 ` Theodore A. Roth
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='CAFMvBt3aumWLd7vzsUHEZ5TvxDkC_2Tjfa=NJVe3qkkJxYieLg@mail.gmail.com' \
--to=troth@openavr.org \
--cc=meta-virtualization@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).