**** BEGIN LOGGING AT Sat Nov 30 02:59:57 2019
Nov 30 05:47:58 <yocti> New news from stackoverflow: ERROR: YoctoProject - core-image-sato: do_populate_sdk <https://stackoverflow.com/questions/59113410/error-yoctoproject-core-image-sato-do-populate-sdk>
**** BEGIN LOGGING AT Sat Nov 30 11:59:37 2019
Nov 30 12:29:33 <xtron> tried to _append " systemd-analyze" to IMAGE_INSTALL but bitbake says nothing RPROVIDE systemd-analyze, what I'm doing wrong?
Nov 30 13:38:40 <LFSVeteran> trying to cross build GCC with stdlibc++ enabled but it fails with this error: aarch64-unknown-linux-gnu-c++: error: unrecognized command line option '-fchar8_t'
Nov 30 13:41:01 <LFSVeteran> gcc-9.2.0
Nov 30 16:49:02 <LFSVeteran> yes moving /usr/include to /usr/include.bak solves it, but this solution is insane...
Nov 30 16:49:28 <LFSVeteran> nevertheless, the original error comes up than: error: unrecognized command line option '-fchar8_t'
Nov 30 16:50:51 <khem> can you share more information as what package was it building and what is your env like ?
Nov 30 16:51:23 <LFSVeteran> I'm trying to cross build gcc-9.2.0 for aarch64-unknown-linux-gnu
Nov 30 16:51:53 <LFSVeteran> I have build a cross compiler with gcc-9.2.0, host x86_64 target aarch64-unknown-linux-gnu
Nov 30 16:52:26 <LFSVeteran> and that one I'm using to buils gcc-9.2.0 host=aarch64-unknown-linux-gnu and target=aarch64-unknown-linux-gnu
Nov 30 16:52:55 <LFSVeteran> without libstdc++ enable all goes well, but when I enable libstdc++ trouble starts
Nov 30 16:53:10 <LFSVeteran> so for test I only build libstdc++-V3 now
Nov 30 16:53:35 <LFSVeteran> in the pastebin you can see my configure line for this
Nov 30 16:55:32 <khem> you are not using OE are you ?
Nov 30 16:55:44 <LFSVeteran> the way I build the first compiler: https://pastebin.com/sjFnrcck
Nov 30 16:55:50 <LFSVeteran> OE?
Nov 30 16:58:10 <LFSVeteran> confusing channel....
Nov 30 16:58:14 <LFSVeteran> not using yocto
Nov 30 16:58:38 <khem> OpenEmbedded is the build system technology that Yoctro project uses
Nov 30 16:58:56 <LFSVeteran> no not using openembeded
Nov 30 16:58:59 <khem> ok so it seems that you need to use recent enough gcc to bootstrap
Nov 30 16:59:26 <khem> your rpm spec file seems to use gcc8
Nov 30 16:59:33 <khem> I would suggest to use gcc9
Nov 30 16:59:50 <khem> CHAR8_TYPE is a recently addition to gcc
Nov 30 16:59:53 <LFSVeteran> 8.2.0 was the first one
Nov 30 17:00:03 <LFSVeteran> ah makes sense
Nov 30 17:00:13 <LFSVeteran> rebuilding the initial compiler then...
Nov 30 17:00:18 <khem> right
Nov 30 17:00:32 <LFSVeteran> thx, going to try that first
Nov 30 20:01:15 <LFSVeteran> rebuild gcc with gcc-9.2 (fresh toolchain)
Nov 30 20:02:03 <LFSVeteran> build stdlibc test, fail, mixing up with local headers > mv /usr/include /usr/include.bak, retry again
Nov 30 20:02:13 <LFSVeteran> aarch64-unknown-linux-gnu-g++: error: unrecognized command line option '-fchar8_t'
Nov 30 20:10:55 <LFSVeteran> ok...gcc 8.2.0 no problems
Nov 30 20:11:21 <LFSVeteran> maybe switching to 8.2.0 instead of 9.2.0 Would it hurt? guess not
Nov 30 20:11:38 <khem> ok somehow its mixing headers from 8.2 into builds for 9.2
Nov 30 20:11:42 <khem> this will not work
Nov 30 20:13:06 <LFSVeteran> hmmm, have I used headers of 8.2...need to check
Nov 30 20:18:36 <khem> aarch64-unknown-linux-gnu-g++ --version
Nov 30 20:18:39 <khem> what does that say
Nov 30 20:27:48 <LFSVeteran> already wiped the toolchain
Nov 30 20:28:15 <LFSVeteran> doubting about first stage compiler
Nov 30 22:51:39 <LFSVeteran> ok...still mixing up with native headers....
Nov 30 22:52:22 <LFSVeteran> but, if I temporary disable /usr/include....libstdc builds fine!
Nov 30 23:33:44 <LFSVeteran> something wrong with glibc? https://pastebin.com/SRaJ7etT
Nov 30 23:34:12 <LFSVeteran> reminds me....is this a new glibc?
Nov 30 23:34:15 <LFSVeteran> rebuild!
Nov 30 23:58:45 <LFSVeteran> nop still the same problem
**** ENDING LOGGING AT Fri Dec 06 11:09:57 2019