From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libqmi: drop unrecognized option
Date: Tue, 30 Mar 2021 21:37:34 +0200 [thread overview]
Message-ID: <20210330193734.GY24043@scaer> (raw)
In-Reply-To: <CAAP7uc+qpS+Y9xN=C89jzupCH5qS2-_W_H7smrYa7SqMov57hw@mail.gmail.com>
On 2021-03-29 23:46 +0200, Aleksander Morgado spake thusly:
> Hey,
>
> On Mon, Mar 29, 2021 at 11:22 PM Fabrice Fontaine
> <fontaine.fabrice@gmail.com> wrote:
> >
> > --enable-more-warnings has been dropped since version 1.26.0 and
> > https://github.com/freedesktop/libqmi/commit/9f31a45d5fc137431705d47b83669f35259932b4
> >
>
> For some context, the build switched to
> AX_COMPILER_FLAGS()+AX_IS_RELEASE() so, when building from a release
> tarball, the build will default to --enable-compile-warnings=yes, and
> when building from a git checkout, the build will default to
> --enable-compile-warnings=error. As long as the buildroot makefile
> relies on stable release tarballs,
And even when working from a git tree, we would not have the .git
directory anyway, so I suppose we'd end up in the "release tarball"
case.
Only people working with LIBQMI_OVERRIDE_SRCDIR set pointing to a
local git clone would fall back into the "defaults to Werror" state.
> -Werror should be always implicitly
> disabled.
But there is a --disable-Werror option, and I think we should use it
unconditionally.
I've done that now, and applied to master, thanks.
Regards,
Yann E. MORIN.
> > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> > ---
> > package/libqmi/libqmi.mk | 3 ---
> > 1 file changed, 3 deletions(-)
> >
> > diff --git a/package/libqmi/libqmi.mk b/package/libqmi/libqmi.mk
> > index b02312d702..998952e47d 100644
> > --- a/package/libqmi/libqmi.mk
> > +++ b/package/libqmi/libqmi.mk
> > @@ -13,9 +13,6 @@ LIBQMI_INSTALL_STAGING = YES
> >
> > LIBQMI_DEPENDENCIES = libglib2
> >
> > -# we don't want -Werror
> > -LIBQMI_CONF_OPTS = --enable-more-warnings=no
> > -
> > # if libgudev available, request udev support for a better
> > # qmi-firmware-update experience
> > ifeq ($(BR2_PACKAGE_LIBGUDEV),y)
> > --
> > 2.30.2
> >
>
>
> --
> Aleksander
> https://aleksander.es
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-03-30 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 21:19 [Buildroot] [PATCH 1/2] package/libqmi: drop unrecognized option Fabrice Fontaine
2021-03-29 21:19 ` [Buildroot] [PATCH 2/2] package/libqmi: needs headers >= 4.14 Fabrice Fontaine
2021-03-29 21:40 ` Aleksander Morgado
2021-03-29 21:44 ` Fabrice Fontaine
2021-03-29 22:13 ` Aleksander Morgado
2021-03-29 21:46 ` [Buildroot] [PATCH 1/2] package/libqmi: drop unrecognized option Aleksander Morgado
2021-03-30 19:37 ` Yann E. MORIN [this message]
2021-03-30 19:51 ` Aleksander Morgado
2021-04-03 10:33 ` 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=20210330193734.GY24043@scaer \
--to=yann.morin.1998@free.fr \
--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 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.