All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/dmalloc: fix strndup detection
Date: Sun, 12 Jun 2022 22:23:07 +0200	[thread overview]
Message-ID: <20220612202307.GL427639@scaer> (raw)
In-Reply-To: <20220610210541.3643416-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2022-06-10 23:05 +0200, Fabrice Fontaine spake thusly:
> Fix strndup detection as already done for strdup in commit
> f9287b263f0808c2f0632aa1560d88e39fbf970b to avoid the following build
> failure raised since bump to version 5.6.5 in commit
> 736932c71552adc4dfa95c5236d1064860900e8a:
> 
> In file included from /nvmedata/autobuild/instance-0/output-1/host/mipsel-buildroot-linux-gnu/sysroot/usr/include/string.h:630:0,
>                  from append.c:34:
> dmalloc.h:396:7: error: expected identifier or '(' before '__extension__'
>  char *strndup(const char *string, const DMALLOC_SIZE max_len);
>        ^
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/2164dac43e2607a3570e8f98957a70f579d06cd3
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/dmalloc/dmalloc.mk | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/dmalloc/dmalloc.mk b/package/dmalloc/dmalloc.mk
> index 93dc45c15d..81ac467277 100644
> --- a/package/dmalloc/dmalloc.mk
> +++ b/package/dmalloc/dmalloc.mk
> @@ -49,6 +49,7 @@ DMALLOC_CONF_ENV = CFLAGS="$(DMALLOC_CFLAGS)"
>  define DMALLOC_POST_PATCH
>  	$(SED) 's/^ac_cv_page_size=0$$/ac_cv_page_size=12/' $(@D)/configure
>  	$(SED) 's/ac_cv_strdup_macro=no$$/ac_cv_strdup_macro=yes/' $(@D)/configure
> +	$(SED) 's/ac_cv_strndup_macro=no$$/ac_cv_strndup_macro=yes/' $(@D)/configure
>  	$(SED) 's/(ld -/($${LD-ld} -/' $(@D)/configure
>  	$(SED) 's/'\''ld -/"$${LD-ld}"'\'' -/' $(@D)/configure
>  	$(SED) 's/ar cr/$$(AR) cr/' $(@D)/Makefile.in
> -- 
> 2.35.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-06-12 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 21:05 [Buildroot] [PATCH 1/2] package/dmalloc: fix strndup detection Fabrice Fontaine
2022-06-10 21:05 ` [Buildroot] [PATCH 2/2] package/dmalloc: disable stack-protector Fabrice Fontaine
2022-06-12 20:37   ` Yann E. MORIN
2023-02-08 16:28     ` Yann E. MORIN
2022-06-12 20:23 ` Yann E. MORIN [this message]
2022-06-19 13:41 ` [Buildroot] [PATCH 1/2] package/dmalloc: fix strndup detection Peter Korsgaard

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=20220612202307.GL427639@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.