From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board/qemu/ppc*: disable Werror while building ppc kernel with gcc >= 9.1
Date: Wed, 1 May 2019 21:38:25 +0200 [thread overview]
Message-ID: <20190501213825.4cac162d@windsurf> (raw)
In-Reply-To: <4a872624-ceb5-23cb-9005-3284ffbce131@gmail.com>
Hello Romain,
On Wed, 1 May 2019 15:57:47 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> > Maybe it would be better to have a single fragment file
> > board/linux-ppc-disable-werror.fragment
> > and include that in all the relevant defconfigs, rather than updating each linux
> > config?
>
> I'm not sure how to handle such fragments in Buildroot.
> Storing fragments in board directory seems not great.
Why ? We already have plenty of these:
$ find board/ | grep frag
board/beaglebone/linux-4.1-sgx.fragment
board/technologic/ts4800/linux.fragment
board/engicam/icorem6/linux_qt5.fragment
board/orangepi/orangepi-pc/linux.fragment
board/amarula/vyasa/linux_gmac.fragment
board/udoo/mx6qdl/linux.fragment
board/lego/ev3/linux.fragment
board/lego/ev3/busybox.fragment
board/stmicroelectronics/stm32mp157-dk/uboot-fragment.config
board/freescale/imx6-sabresd/linux_qt5.fragment
board/freescale/warpboard/linux.fragment
board/solidrun/macchiatobin/uboot-fragment.config
board/solidrun/clearfog/linux.fragment
board/synopsys/hsdk/linux.fragment
board/qemu/nios2-10m50/linux.fragment
board/qemu/ppc64-e5500/linux.fragment
board/lemaker/bananapro/linux-wifi.fragment
board/chromebook/snow/linux-4.15.fragment
board/olimex/imx233_olinuxino/linux-wifi.fragment
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-01 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 12:52 [Buildroot] [PATCH] board/qemu/ppc*: disable Werror while building ppc kernel with gcc >= 9.1 Romain Naour
2019-05-01 13:32 ` Arnout Vandecappelle
2019-05-01 13:57 ` Romain Naour
2019-05-01 19:38 ` Thomas Petazzoni [this message]
2019-05-01 19:47 ` Romain Naour
2019-05-02 12:27 ` Arnout Vandecappelle
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=20190501213825.4cac162d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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.