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: Fri, 16 Jun 2017 14:25:41 +0200 [thread overview]
Message-ID: <20170616142541.51df47c6@windsurf.lan> (raw)
In-Reply-To: <0ED1FB7E7CA752468B2E7F31EDFC6CD6013BA8A2@de02wembxa.internal.synopsys.com>
Hello,
On Fri, 16 Jun 2017 11:51:49 +0000, Dmitrii Kolesnichenko wrote:
> > Thanks for the contribution. However, could you be more specific
> > about which Buildroot configuration triggers this build failure?
>
> It occurs when I build rootfs for ARC glibc toolchain. When I build
> uClibc toolchain this failure doesn't occur.
That is weird. Why we aren't seeing this with our other glibc
toolchains? Is it because you're testing with the latest glibc master,
which exhibits this issue?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-16 12:25 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 [this message]
2017-06-16 15:40 ` Dmitrii Kolesnichenko
2017-06-19 15:06 ` Dmitrii Kolesnichenko
2017-06-19 19:31 ` Thomas Petazzoni
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=20170616142541.51df47c6@windsurf.lan \
--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