From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Karoly Kasza <kaszak@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/openvmtools: fix build on i686
Date: Sun, 25 Oct 2026 18:58:18 +0100 [thread overview]
Message-ID: <at5DNdGEgostVJ1u@windsurf> (raw)
In-Reply-To: <20261025172656.2241739-1-bernd@kuhls.net>
On Sun, Oct 25, 2026 at 06:26:56PM +0100, Bernd Kuhls wrote:
> The patch set used to bump openvmtools from 11.3.5 to 13.1.0 contained a
> patch which is not needed anymore due to upstream fix
> https://github.com/vmware/open-vm-tools/commit/36eea633611e678f3ea17a913c0990f319135c48
> available since version 12.1.0.
>
> The patch causes build errors on i686:
>
> hgfsUtil.c: In function 'HgfsConvertFromNtTimeNsec':
> hgfsUtil.c:135:49: error: 'sec64' undeclared (first use in this function)
> hgfsUtil.c:135:57: error: 'nsec' undeclared (first use in this function)
>
> To fix the problem we remove patch 0010 and renumber the remaining
> patches.
>
> Fixes:
> https://autobuild.buildroot.net/results/d37/d37be203b0b4d46c052427ea2c469c624b26504e/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-25 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 17:26 [Buildroot] [PATCH 1/1] package/openvmtools: fix build on i686 Bernd Kuhls
2026-10-25 17:58 ` Thomas Petazzoni via buildroot [this message]
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=at5DNdGEgostVJ1u@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=kaszak@gmail.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox