Khem Raj

@jpuhlman this seems to be because the gcc in play is not passing `-std=c++14` since clang++ would use the c++ runtime from your host gcc. Perhaps you should ensure the...

Can you try using `-gcc-toolchain /path/to/your/gcc/install --target=tuple-with-pooky-sdk`

@jpuhlman is this resolved ?

@dagmcr can this issue be closed for master ? or is there anything more needed

hmmm does setting `export YOCTO_ALTERNATE_EXE_PATH = "${STAGING_LIBDIR}/llvm-config"` help with master or no ? I wonder if it needs llvm sources to be available and not just installed artifacts.

I see that it might need some more work to make this cross compile friendly, maybe use a prebuilt llvm-native tree and see if it can build using that build...

yeah try `dunfell` first.

@telkamp you can set `LLVMVERSION = "12.0.0"` in `conf/layer.conf` when using `dunfell_clang12` branch, I think this is missing in that branch. When it comes to using clang13 with dunfell, I...

@jwinarske I think the branch was not uptodate it should be same as `clang12`, now the branch has been updated so both `clang12` and `dunfell-clang12` should be same. Please update...

@jwinarske you should firstly set `LLVMVERSION = "12.0.0"` in `conf/layer.conf` this will atleast choose clang12 and perhaps that will fix it. If that does not fix it then try ```...