master branch became incompatible with kirkstone

[lumag]

After the commit 0438fba the layer became incompatible with the kirkstone OE branch, because it depends on rust-targets subdir, which was not available before openembedded/openembedded-core@9160e4a.

| install: cannot stat '/oe/build/tmp-rpb-glibc/work/x86_64-linux/rust-native/1.59.0-r0/rust-targets/x86_64-unknown-linux-gnu.json': No such file or directory

[MaxIhlenfeldt]

Unfortunately we require using Rust from meta-lts-mixins' kirkstone/rust-1.68 or kirkstone/rust-1.70 branch. I don't think that Chromium can be compiled with Rust 1.59 anyway.

I'll close this for now, but if you're unable to use a mixin layer, feel free to give compiling Chromium a try with Rust 1.59 on a regular machine. If that works I'll reopen this issue and will see if I can adapt our recipe to work without the rust-targets subdir.

[rakuco]

Unfortunately we require using Rust from meta-lts-mixins' kirkstone/rust-1.68 or kirkstone/rust-1.70 branch. I don't think that Chromium can be compiled with Rust 1.59 anyway.

Would it be possible to add some version (or branch?) check like do_check_llvm_version to help people? If not, these requirements and different branches should at least be mentioned in the README.

[lumag]

@MaxIhlenfeldt @rakuco then could you please remove kirkstone from the list of compatible versions? That's the main source of information and a guarding check in case of the mistakes.

[lumag]

Another option is to get necessary changes backported to the OE-Core/kirkstone.

[MaxIhlenfeldt]

The easiest solution would be to remove kirkstone from LAYERSERIES_COMPAT but advertise in the README that kirkstone will still work if you use the layer from meta-lts-mixins. Not sure how open OE would be to backport the mixin layer.

[lumag]

Then backport from langsdale instead of mixins

[MaxIhlenfeldt]

I don't have the time to backport patches, regardless of whether from langdale or from mixins. @rakuco should we just do the approach outlined in #789 (comment)?

[rakuco]

@MaxIhlenfeldt Sorry for the silence here! I remember seeing some discussions about meta-lts-mixins and something changing for the Rust recipes across different branches; what's the situation at the moment? Does kirkstone still work with meta-lts-mixins, or at all?

[MaxIhlenfeldt]

@rakuco kirkstone should work with meta-chromium 120, but only when using meta-lts-mixins. Given that it won't be compatible with 121 and higher versions due to the outdated compiler, I'd propose the following:

• create a kirkstone branch off of c76bc3a
• change the kirkstone branch's README to say that you have to use meta-lts-mixins
• remove kirkstone from LAYERSERIES_COMPAT on master, and possible on the kirkstone branch as well

Feel free to go ahead with these changes if you agree, or let me know I should go ahead / what you'd like to differently.

[rakuco]

Sounds good to me; I just didn't understand the part about removing kirkstone from LAYERSERIES_COMPAT in the kirkstone branch. Isn't it going to make the branch unbuildable?

If you work on a patch, I can approve the PR quite quickly.