From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtirpc: Fix build error due to missing stdint.h inclusion
Date: Mon, 19 Jun 2017 21:31:40 +0200 [thread overview]
Message-ID: <20170619213140.731daabb@windsurf.home> (raw)
In-Reply-To: <20170619150626.31273-1-dmitrii@synopsys.com>
Hello,
On Mon, 19 Jun 2017 18:06:26 +0300, Dmitrii Kolesnichenko wrote:
> Add patch to fix following error:
> | ../../libtirpc-1.0.1/src/xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared (first use in this function); did you mean '__intptr_t'?
> | if (len < (uintptr_t)xdrs->x_base) {
> | ^~~~~~~~~
>
> It includes stdint.h to provide uintptr_t.
>
> This patch has been submitted upstream:
> https://sourceforge.net/p/libtirpc/mailman/libtirpc-devel/
>
> Signed-off-by: Dmitrii Kolesnichenko <dmitrii@synopsys.com>
Thanks, but this commit log and patch description still don't explain
with which version of glibc you're seeing the problem. Indeed, this
error has not been caught by our autobuilders, so one may wonder why
this additional patch is needed.
Can you add such an explanation in the commit description?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-19 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 18:05 [Buildroot] [PATCH] libtirpc: Fix build error due to missing stdint.h inclusion Dmitrii Kolesnichenko
2017-06-15 21:19 ` Thomas Petazzoni
2017-06-16 11:51 ` Dmitrii Kolesnichenko
2017-06-16 12:25 ` Thomas Petazzoni
2017-06-16 15:40 ` Dmitrii Kolesnichenko
2017-06-19 15:06 ` Dmitrii Kolesnichenko
2017-06-19 19:31 ` Thomas Petazzoni [this message]
2017-06-20 8:51 ` [Buildroot] [PATCH v3] " Dmitrii Kolesnichenko
2017-06-20 10:47 ` Alexey Brodkin
2017-06-20 16:55 ` [Buildroot] [PATCH v4] " Dmitrii Kolesnichenko
2017-06-20 20:10 ` Thomas Petazzoni
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=20170619213140.731daabb@windsurf.home \
--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