From: Viresh Kumar <viresh.kumar@linaro.org>
To: Kent Gibson <warthog618@gmail.com>
Cc: linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
erik.schilling@linaro.org
Subject: Re: [libgpiod][bug] building rust bindings requires clang headers
Date: Fri, 9 Jun 2023 11:54:56 +0530 [thread overview]
Message-ID: <20230609062456.fqw3mqvtcactx2zj@vireshk-i7> (raw)
In-Reply-To: <ZILE258m92XrBvNP@sol>
On 09-06-23, 14:21, Kent Gibson wrote:
> I think that is what the AC_HEADER_STDBOOL already does - but that
> detects the gcc header, and the additional check needs to be for the clang
> header.
>
> Unless you can convince clang to use the gcc headers?
Ahh, my bad :(
--
viresh
next prev parent reply other threads:[~2023-06-09 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 2:37 [libgpiod][bug] building rust bindings requires clang headers Kent Gibson
2023-06-09 6:18 ` Viresh Kumar
2023-06-09 6:21 ` Kent Gibson
2023-06-09 6:24 ` Viresh Kumar [this message]
2023-06-10 5:27 ` Kent Gibson
2023-06-12 5:26 ` Erik Schilling
2023-06-12 7:32 ` Kent Gibson
2023-06-12 11:16 ` Erik Schilling
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=20230609062456.fqw3mqvtcactx2zj@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=brgl@bgdev.pl \
--cc=erik.schilling@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=warthog618@gmail.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;
as well as URLs for NNTP newsgroup(s).