From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kaszak@gmail.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/openvmtools: bump version to 11.3.5
Date: Thu, 19 May 2022 06:06:48 +0300 [thread overview]
Message-ID: <87pmkaqkuv.fsf@tarshish> (raw)
In-Reply-To: <fa9bd454f0e7d72a0eac64ddae226513b2968126.1652914532.git.stefan@agner.ch>
Hi Stefan,
On Thu, May 19 2022, Stefan Agner wrote:
> Rebase patches as necessary and bump version to 11.3.5. This allows
> to build openvmtools for aarch64.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> ..._poll-h-to-fix-build-failure-on-musl.patch | 85 +++++++++++--------
> ...-test-for-feature-instead-of-platfor.patch | 1 +
> .../0009-Set-permissions-on-rules-file.patch | 23 -----
> .../0010-Change-DEVPATH-to-devpath.patch | 25 ------
> package/openvmtools/openvmtools.hash | 2 +-
> package/openvmtools/openvmtools.mk | 4 +-
> 6 files changed, 54 insertions(+), 86 deletions(-)
> delete mode 100644 package/openvmtools/0009-Set-permissions-on-rules-file.patch
> delete mode 100644 package/openvmtools/0010-Change-DEVPATH-to-devpath.patch
>
> diff --git a/package/openvmtools/0003-Rename-poll-h-into-vm_poll-h-to-fix-build-failure-on-musl.patch b/package/openvmtools/0003-Rename-poll-h-into-vm_poll-h-to-fix-build-failure-on-musl.patch
> index e9495ce43f..4749f3f462 100644
> --- a/package/openvmtools/0003-Rename-poll-h-into-vm_poll-h-to-fix-build-failure-on-musl.patch
> +++ b/package/openvmtools/0003-Rename-poll-h-into-vm_poll-h-to-fix-build-failure-on-musl.patch
> @@ -1,4 +1,5 @@
> -From 9d13e32e362ad3ce5169f49b7f0fe1d9380e558c Mon Sep 17 00:00:00 2001
> +From 1dfab46d367d11e9132506ee0f7d3eb2ceff5f3c Mon Sep 17 00:00:00 2001
> +Message-Id: <1dfab46d367d11e9132506ee0f7d3eb2ceff5f3c.1652913832.git.stefan@agner.ch>
> From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> Date: Mon, 30 Sep 2019 13:32:35 +0200
> Subject: [PATCH] Rename poll.h into vm_poll.h to fix build failure on musl
> @@ -25,7 +26,7 @@ asyncsocket.c:2538:33: error: ‘POLLIN’ undeclared (first use in this functio
> pfd[i].events = read ? POLLIN : POLLOUT;
>
> So rename poll.h into vm_poll.h as suggested by srowe in
> -https://github.com/vmware/open-vm-tools/issues/359#issuecomment-533529956
> +https://github.com/vmware/issues/359#issuecomment-533529956
This leads to 404 error page.
> Fixes:
> - http://autobuild.buildroot.org/results/4f575ef42bbc4387a07e396205052b2da081c64d
> @@ -33,24 +34,24 @@ Fixes:
> Fix #359
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> -[Upstream status: https://github.com/vmware/open-vm-tools/pull/383]
> +[Upstream status: https://github.com/vmware/pull/383]
Also here.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-19 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 22:57 [Buildroot] [PATCH] package/openvmtools: bump version to 11.3.5 Stefan Agner
2022-05-19 3:06 ` Baruch Siach via buildroot [this message]
2022-05-19 7:26 ` Stefan Agner
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=87pmkaqkuv.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=kaszak@gmail.com \
--cc=stefan@agner.ch \
/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