From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 1/3] automation/alpine: add elfutils-dev and coreutils for livepatch-build-tools
Date: Thu, 23 Nov 2023 13:25:53 +0100 [thread overview]
Message-ID: <ZV9E0WQV2eQtkdzU@macbook> (raw)
In-Reply-To: <a55bd27f-a8e1-4ea8-9da7-b80bd424315d@citrix.com>
On Thu, Nov 23, 2023 at 11:51:33AM +0000, Andrew Cooper wrote:
> On 23/11/2023 11:23 am, Roger Pau Monne wrote:
> > In preparation for adding some livepatch-build-tools test update the Alpine
> > container to also install elfutils-dev, coreutils and GNU awk.
> >
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> > ---
> > I don't very much like to add coreutils and gawk, as it's also good to test
> > that we can build Xen with Busybox, but I also got tired of adjusting
> > livepatch-build-tools.
>
> Right now, the alpine environment is the main one which spots violations
> of Xen's requirement for simply a POSIX-compliant awk, which I think
> this would break?
Likely, we also test on Cirrus using FreeBSD, so we would at least
spot instances where the extensions are not implemented by BSD sed.
> How much effort would it be fix livepatch-build-tools? I think that
> would be preferable, and could be persuaded to do some simple busywork...
I can give it a try.
> What about coreutils? Presumably that's down to some differences from
> busybox ?
Yeah, it's for the usage of `readlink -m` by livepatch-build-tools.
We will have to switch to using `readlink -f`, as that's the only
canonicalize option supported by BusyBox readlink. Note that anyway
`readlink` is not part of POSIX.
Thanks, Roger.
next prev parent reply other threads:[~2023-11-23 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 11:23 [PATCH 0/3] automation: add livepatch testing Roger Pau Monne
2023-11-23 11:23 ` [PATCH 1/3] automation/alpine: add elfutils-dev and coreutils for livepatch-build-tools Roger Pau Monne
2023-11-23 11:51 ` Andrew Cooper
2023-11-23 12:25 ` Roger Pau Monné [this message]
2023-11-23 11:23 ` [PATCH 2/3] livepatch: add a dummy hypercall for testing purposes Roger Pau Monne
2023-11-23 16:56 ` Andrew Cooper
2023-11-23 11:23 ` [PATCH 3/3] automation: add x86-64 livepatching test Roger Pau Monne
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=ZV9E0WQV2eQtkdzU@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.