buildroot.busybox.net archive mirror
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Matt Weber <matthew.weber@collins.com>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/lighttpd: run autoreconf
Date: Sat, 20 Nov 2021 10:23:11 +0100	[thread overview]
Message-ID: <CAPi7W81xnSeS3w+mswu1ALNKSQVphfyim5jkFDmJgLJmj=dopA@mail.gmail.com> (raw)
In-Reply-To: <20211120003256.61693b53@gmx.net>

Hello Peter,

Le sam. 20 nov. 2021 à 00:33, Peter Seiderer <ps.report@gmx.net> a écrit :
>
> Hello Fabrice,
>
> On Thu, 18 Nov 2021 22:06:23 +0100, Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
>
> > For an unknown reason, the build fails since bump to version 1.4.60 in
> > commit d62b7f54f00291a50274409fb5510527fd725ffe on:
> >
> > array.c:140:2: error: 'for' loop initial declarations are only allowed in C99 mode
> >   for (uint32_t i = 0; i < sz; ++i) {
> >   ^
> >
> > Running autoreconf fixes the build.
>
> The difference is during the configure step:
>
> - checking for .../host/bin/arm-none-linux-gnueabi-gcc option to accept ISO C89... none needed
> + checking for .../host/bin/arm-none-linux-gnueabi-gcc option to enable C11 features... -std=gnu11
>
> And the use of the '-std=gnu11' flag for the compile steps..., any more
> lightweight option to enable C11?
Then, I assume that upstream forgot to regenerate the configure script after
https://github.com/lighttpd/lighttpd1.4/commit/73865025729897d11494de56a29c77c4fc8e5702
I opened an issue here: https://redmine.lighttpd.net/issues/3116

>
> Regards,
> Peter
>
> >
> > Fixes:
> >  - http://autobuild.buildroot.org/results/0349d8fed35b0766796dd9ba3b8de6ff8bd68fe7
> >
> > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> > ---
> >  package/lighttpd/lighttpd.mk | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/package/lighttpd/lighttpd.mk b/package/lighttpd/lighttpd.mk
> > index 9c18a6038e..c39a5db20f 100644
> > --- a/package/lighttpd/lighttpd.mk
> > +++ b/package/lighttpd/lighttpd.mk
> > @@ -12,6 +12,8 @@ LIGHTTPD_LICENSE = BSD-3-Clause
> >  LIGHTTPD_LICENSE_FILES = COPYING
> >  LIGHTTPD_CPE_ID_VENDOR = lighttpd
> >  LIGHTTPD_DEPENDENCIES = host-pkgconf
> > +# Issue in configure script provided in tarball
> > +LIGHTTPD_AUTORECONF = YES
> >  LIGHTTPD_CONF_OPTS = \
> >       --without-wolfssl \
> >       --libdir=/usr/lib/lighttpd \
>
Best Regards,

Fabrice
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-11-20  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 21:06 [Buildroot] [PATCH 1/1] package/lighttpd: run autoreconf Fabrice Fontaine
2021-11-19 23:32 ` Peter Seiderer
2021-11-20  9:23   ` Fabrice Fontaine [this message]
2021-11-20 19:53     ` Peter Seiderer
2021-11-20 20:15       ` Fabrice Fontaine
2021-11-20 20:23         ` Peter Seiderer
2021-11-20 20:39           ` Fabrice Fontaine
2021-11-21 21:32             ` Peter Seiderer
2021-11-22 20:42 ` Arnout Vandecappelle
2021-11-23 18:33   ` Peter Seiderer

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='CAPi7W81xnSeS3w+mswu1ALNKSQVphfyim5jkFDmJgLJmj=dopA@mail.gmail.com' \
    --to=fontaine.fabrice@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=matthew.weber@collins.com \
    --cc=ps.report@gmx.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;
as well as URLs for NNTP newsgroup(s).