**** BEGIN LOGGING AT Sun May 24 02:59:59 2020
May 24 04:57:25 <khem> Jin^eLD: is your host gcc vesion 10 ?
May 24 11:07:03 <Jin^eLD> khem: no, gcc 9.3.1, I managed to work around it by doing this:
May 24 11:07:05 <Jin^eLD>     export CFLAGS_FOR_BUILD="${BUILD_CFLAGS} -fpermissive"
May 24 11:07:09 <Jin^eLD> i.e. adding -fpermissive
May 24 12:50:08 <Jin^eLD> is there an easy way to build a cross compiler for a machine that is different than the target? I did something similar using precompiled baremetal toolchains and hacking them in, but I remember someone (unfortunately forgot who) was working on a more generic approach?
May 24 12:50:57 <Jin^eLD> basically the yocto-built distro is going to run on some random linux box, but it needs to ship firmware for a bunch of mcu's and I'm trying to build that firmware within the yocto build
May 24 12:52:22 <Jin^eLD> I'm hacking an imagine containing the klipper 3d printing software and their current setup (via armbian/debian) is that people compile the mcu firmware directly on the target; I'd like to ship that precompiled in the image to avoid any additional manual steps
May 24 12:53:05 <Jin^eLD> so far I only found http://www.openembedded.org/wiki/Adding_a_secondary_toolchain but its not quite the same, I am only looking to build "another cross gcc" not to use some totally alternative toolchain
May 24 14:09:00 <Crofton[m]> Something like this? https://youtu.be/mFgiIXv7b5U
May 24 18:23:27 <Jin^eLD> Crofton[m]: yes! thank you
May 24 20:06:25 <Jin^eLD> interesting, I was not aware of the multiconfig stuff
**** ENDING LOGGING AT Mon May 25 02:59:57 2020