linux kernel compiler warnings ignored
Patrick Venture
venture at google.com
Sat Apr 27 01:46:32 AEST 2019
On Fri, Apr 26, 2019 at 8:14 AM Andrew Jeffery <andrew at aj.id.au> wrote:
>
>
>
> On Fri, 26 Apr 2019, at 08:01, Patrick Venture wrote:
> > I'm getting feedback from a patchset I sent upstream that there are
> > compiler warnings. Which surprised me because my OpenBMC builds with
> > those patches don't complain. I imagine therefore we have them
> > silenced and was curious where we silence them.
>
> How are you building the kernel?
>
> I strongly recommend you build kernels directly from the kernel source tree rather than using bitbake, if that's what you're doing.
I'm building the kernel via bitbake as you surmised.
>
> In the kernel source tree, do:
>
> $ export ARCH=arm
> $ export CROSS_COMPILE=arm-linux-gnueabi-
> $ make aspeed_g5_defconfig
> $ make W=1 -j$(nproc)
>
> This exports are from memory, ymmv.
Thanks. I've fired off a complete build of the kernel to catch this.
I don't have the openbmc SDK toolchain installed at the moment, but
that's not a difficult task.
>
> In addition to giving you more output than Greg is after, it has a much lower write/compile/test latency.
>
> Hope that helps,
>
> Andrew
>
> >
> > Patrick
> >
More information about the openbmc
mailing list