From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] evemu: fix PATH_MAX related compile failure
Date: Wed, 11 Oct 2017 22:06:46 +0200 [thread overview]
Message-ID: <20171011220646.21c208a5@windsurf.lan> (raw)
In-Reply-To: <20171011091452.11162-1-ps.report@gmx.net>
Hello,
On Wed, 11 Oct 2017 11:14:52 +0200, Peter Seiderer wrote:
> Fixes [1] when building with musl:
>
> find_event_devices.c: In function 'find_event_devices':
> find_event_devices.c:60:14: error: 'PATH_MAX' undeclared (first use in this function)
> char fname[PATH_MAX];
> ^~~~~~~~
>
> [1] http://autobuild.buildroot.net/results/607/607bb29231f80a138e1b5423bc01c89e36efe78c/
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> Changes v1 -> v2:
> - use limits.h instead of linux/limits.h, change patch commit message,
> add musl reference (suggested by Arnout Vandecappelle)
> ---
> .../evemu/0001-Include-limits.h-for-PATH_MAX.patch | 35 ++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 package/evemu/0001-Include-limits.h-for-PATH_MAX.patch
Applied to master, thanks. Please don't forget to submit the patch
upstream if not already done. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-11 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:14 [Buildroot] [PATCH v2] evemu: fix PATH_MAX related compile failure Peter Seiderer
2017-10-11 20:06 ` Thomas Petazzoni [this message]
2017-10-11 20:14 ` Peter Seiderer
2017-10-11 20:28 ` 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=20171011220646.21c208a5@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