Khem Raj

@LEDZB @concatime I understand the problem now. In openembedded we install few BSD headers via [bsd-headers](https://git.yoctoproject.org/poky/tree/meta/recipes-core/musl/bsd-headers.bb) package which provides `sys/cdefs.h` on OpenEmbedded builds thats why we do not see these...

> > @LEDZB @concatime I understand the problem now. In openembedded we install few BSD headers via [bsd-headers](https://git.yoctoproject.org/poky/tree/meta/recipes-core/musl/bsd-headers.bb) package which provides `sys/cdefs.h` on OpenEmbedded builds thats why we do not...

IMHO layerindex should be fixed to read `LAYERSERIES_COMPAT` from `conf/layer.conf` instead of forcing everyone to create branch to resemble release branch. maintaining browsers is a huge ask and creating specific...

perhaps we want to add this to `LAYERDEPENDS` to `layer.conf`

``` ERROR: Unknown CPU type: riscv64 ``` thats clearly stating whats missing. Perhaps start with tip of trunk and see what all support went into latest firefox and then enhance...

using clang16 just for chromium might be fine for dunfell and kirkstone however, this would need work since we wont be able to build rest of OE packages with clang16...

> > we wont be able to build rest of OE packages with clang16 without major surgery. > > I would have expected using a newer clang version to be...

> Sounds reasonable! > > @kraj would you have time for that work? If not, I suppose I could give it a try. we use clang16 on `mickledore` and moved...

I meant to say clang15 not 16.

> Thanks for the clarification! > > Do you have time to look into updating mickledore and kirkstone to clang 16? Not in coming 2-4 weeks. Perhaps after October