On Fri, 5 Nov 2021 at 03:29, Oskar Senft [off-list ref] wrote:

Hi Joel

quoted

I test the kernels independently of yocto; I recommend doing that with
a cross compiler when submitting patches upstream. My flow looks like
this:
[...]
A few notes:
 - I use the cross compiler from my distro. Debian unstable has GCC
11.2.0, which is the same as openbmc. You can use the compiler from
your openbmc build tree if you aren't able to install a modern
compiler

I couldn't figure out how to use the compiler from the OpenBMC tree.
The biggest issue is that it has "openbmc" in its name and Linux build
was getting confused by it. I gave up on that approach and found how
to install the right cross compiler in our environment. That worked
well. Thanks for the hints!

Cool. For reference, you should be able to do this:

CROSS_COMPILE="openbmc/build/p10bmc/tmp/sysroots-components/x86_64/gcc-cross-arm/usr/bin/arm-openbmc-linux-gnueabi/arm-openbmc-linux-gnueabi-"

quoted

 - building with -s means warnings stand out

Excellent idea, thank you!

quoted

 - if you're working on device trees and want to ensure your binary is
being built each time, omit the -s and build the 'dtbs' target

Ack.

I'll send a PATCH v3 now.

Oskar.