Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/smack: fix musl build
Date: Tue, 2 Feb 2016 14:24:31 +0100	[thread overview]
Message-ID: <56B0AE0F.5070706@mind.be> (raw)
In-Reply-To: <1454257581-22383-2-git-send-email-bernd.kuhls@t-online.de>

On 31-01-16 17:26, Bernd Kuhls wrote:
> The build error was not yet found by the autobuilders:
> 
> common.c: In function ?clear?:
> common.c:36:12: error: ?PATH_MAX? undeclared (first use in this function)
>   char path[PATH_MAX];
>             ^
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>


 Regards,
 Arnout

> ---
>  ...ck-common.c-Include-limits.h-for-PATH_MAX.patch | 29 ++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>  create mode 100644 package/smack/0001-libsmack-common.c-Include-limits.h-for-PATH_MAX.patch
> 
> diff --git a/package/smack/0001-libsmack-common.c-Include-limits.h-for-PATH_MAX.patch b/package/smack/0001-libsmack-common.c-Include-limits.h-for-PATH_MAX.patch
> new file mode 100644
> index 0000000..0e30ef5
> --- /dev/null
> +++ b/package/smack/0001-libsmack-common.c-Include-limits.h-for-PATH_MAX.patch
> @@ -0,0 +1,29 @@
> +From 316c911aa741b14513622a4206ed6d324e951fa0 Mon Sep 17 00:00:00 2001
> +From: Felix Janda <felix.janda@posteo.de>
> +Date: Wed, 20 May 2015 21:25:22 +0200
> +Subject: [PATCH 1/1] libsmack/common.c: Include <limits.h> for PATH_MAX
> +
> +Signed-off-by: Felix Janda <felix.janda@posteo.de>
> +Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> +---
> +Downloaded from upstream commit
> +https://github.com/smack-team/smack/commit/316c911aa741b14513622a4206ed6d324e951fa0
> +
> + libsmack/common.c | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/libsmack/common.c b/libsmack/common.c
> +index 55fee1a..55b59e3 100644
> +--- a/libsmack/common.c
> ++++ b/libsmack/common.c
> +@@ -22,6 +22,7 @@
> + #include <dirent.h>
> + #include <errno.h>
> + #include <fcntl.h>
> ++#include <limits.h>
> + #include <stdio.h>
> + #include <string.h>
> + #include <unistd.h>
> +-- 
> +2.7.0
> +
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-02-02 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 16:26 [Buildroot] [PATCH 1/2] package/smack: bump version to 1.1.0 Bernd Kuhls
2016-01-31 16:26 ` [Buildroot] [PATCH 2/2] package/smack: fix musl build Bernd Kuhls
2016-02-02 13:24   ` Arnout Vandecappelle [this message]
2016-01-31 20:06 ` [Buildroot] [PATCH 1/2] package/smack: bump version to 1.1.0 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=56B0AE0F.5070706@mind.be \
    --to=arnout@mind.be \
    --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