All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/esp-hosted: disable -Werror
Date: Wed, 06 Mar 2024 16:52:21 +0100	[thread overview]
Message-ID: <875xxzxsqy.fsf@48ers.dk> (raw)
In-Reply-To: <20240305171938.2252446-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Tue, 5 Mar 2024 18:19:38 +0100")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Disable -Werror to fix the following build failure raised at least since
 > commit a382a7d55432918d2a1e47ae4cbe7ed50fa17a08:

 > In function ‘destroy_cmd_wq’,
 >     inlined from ‘esp_commands_teardown’ at /home/autobuild/autobuild/instance-4/output-1/build/esp-hosted-ce3c50a33fa4bc562a1b6cbcee292c1ae0b0a404/esp_hosted_ng/host/esp_cmd.c:1467:2:
 > ./include/linux/workqueue.h:639:9: error: call to ‘__warn_flushing_systemwide_wq’ declared with attribute warning: Please avoid flushing system-wide workqueues. [-Werror=attribute-warning]
 >   639 |         __warn_flushing_systemwide_wq();                                \
 >       |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 > /home/autobuild/autobuild/instance-4/output-1/build/esp-hosted-ce3c50a33fa4bc562a1b6cbcee292c1ae0b0a404/esp_hosted_ng/host/esp_cmd.c:408:17:
 > note: in expansion of macro ‘flush_scheduled_work’
 >   408 |                 flush_scheduled_work();
 >       |                 ^~~~~~~~~~~~~~~~~~~~

 > Fixes:
 >  - http://autobuild.buildroot.org/results/6ac7a4601938d3296ed1657c06f8cdf433757d73
 >  - http://autobuild.buildroot.org/results/7997cc8a67645a6e1cf4e24d172c6feae459dcfb

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
 > ---
 >  package/esp-hosted/esp-hosted.mk | 1 +
 >  1 file changed, 1 insertion(+)

 > diff --git a/package/esp-hosted/esp-hosted.mk b/package/esp-hosted/esp-hosted.mk
 > index cc61e39b36..02de3dbc52 100644
 > --- a/package/esp-hosted/esp-hosted.mk
 > +++ b/package/esp-hosted/esp-hosted.mk
 > @@ -12,6 +12,7 @@ ESP_HOSTED_LICENSE_FILE = LICENSE
 >  ESP_HOSTED_MODULE_SUBDIRS = esp_hosted_ng/host
 
 >  define ESP_HOSTED_LINUX_CONFIG_FIXUPS
 > +	$(call KCONFIG_DISABLE_OPT,CONFIG_WERROR)

I wonder if we shouldn't unconditionally disable CONFIG_WERROR in
linux.mk, similar to how we do for a number of other packages - The
Linux build could fail with warnings if a too old/new toolchain is used.

I doubt a lot of real defconfigs want to use CONFIG_WERROR, the problem
is most likely only for the arch defconfigs:

git grep CONFIG_WERROR=y
arch/x86/configs/i386_defconfig:CONFIG_WERROR=y
arch/x86/configs/x86_64_defconfig:CONFIG_WERROR=y

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-03-06 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 17:19 [Buildroot] [PATCH 1/1] package/esp-hosted: disable -Werror Fabrice Fontaine
2024-03-05 17:24 ` Giulio Benetti
2024-03-06 15:52 ` Peter Korsgaard [this message]

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=875xxzxsqy.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=giulio.benetti@benettiengineering.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.