From: patchwork-bot+bluetooth@kernel.org
To: None <orbea@riseup.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/1] configure.ac: check for stdio.h
Date: Tue, 04 Mar 2025 15:10:34 +0000 [thread overview]
Message-ID: <174110103451.178640.1185827816099968105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304005006.32322-1-orbea@riseup.net>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 3 Mar 2025 16:50:06 -0800 you wrote:
> From: orbea <orbea@riseup.net>
>
> This fixes a configure failure for readline.h with slibtoolize which
> depends on HAVE_STDIO_H being defined. With GNU libtoolize this check is
> implicit and with slibtoolize it will fail instead.
>
> error: unknown type name 'FILE'
>
> [...]
Here is the summary with links:
- [BlueZ,1/1] configure.ac: check for stdio.h
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b71c53279266
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-04 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 0:50 [PATCH BlueZ 1/1] configure.ac: check for stdio.h orbea
2025-03-04 2:10 ` [BlueZ,1/1] " bluez.test.bot
2025-03-04 15:10 ` patchwork-bot+bluetooth [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=174110103451.178640.1185827816099968105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=orbea@riseup.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