From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openvmtools: enable for uClibc toolchains
Date: Sun, 13 Dec 2015 23:01:45 +0100 [thread overview]
Message-ID: <20151213230145.765dd4a1@free-electrons.com> (raw)
In-Reply-To: <20151204165330.GA5268@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Fri, 4 Dec 2015 17:53:30 +0100, Waldemar Brodkorb wrote:
> Since uClibc-ng 1.0.9 openvmtools can be compiled as
> the missing euidaccess function was added.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/openvmtools/Config.in | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
Arnout explained very well that this patch is not super great due to
the need to keep things working with older uClibc toolchains. Could you
instead cook a patch that changes openvmtools to detect if euidaccess()
is available or not. If it is available, then it uses it, otherwise, it
open-codes it (the euidaccess implementation in uClibc is just one
line, so it's not a big deal to copy that in the openvmtools source
code).
Are you willing to implement such a solution?
I'd say that within 6/12 months, we should be able to kill non-ng
uClibc support. Blackfin will be a problem... but Blackfin has always
been a problem.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-13 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 16:53 [Buildroot] [PATCH] openvmtools: enable for uClibc toolchains Waldemar Brodkorb
2015-12-05 15:52 ` Arnout Vandecappelle
2015-12-05 19:24 ` Waldemar Brodkorb
2015-12-13 22:01 ` Thomas Petazzoni [this message]
2015-12-13 22:30 ` Waldemar Brodkorb
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=20151213230145.765dd4a1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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