Skip to content

Conversation

@adalessandro
Copy link

This is a proposal for a new branch kirkstone-clang18, as discussed in the
yocto-patches mailing list. See https://lists.yoctoproject.org/g/yocto-patches/message/783

The following branch request is based on scarthgap with the required compatibility
changes on top for the sake of simplicity.

NOTE: this is a new branch request, not to be merged to scarthgap branch.

Related to:

Backporting from scarthgap, add kirkstone compat.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
This reverts commit 94d11d8.

As kirkstone still provides busybox 1.35, bbapend must match that
version. Revert the related scarthgap busybox version bump.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
The bindgen-cli recipe was mainly added as it is used by Mesa to build
Rusticl. It inherits from the cargo-update-recipe-crates.bbclass
provided in scarthgap, but missing in kirkstone.

As bindgen-cli recipe is not supported in kirkstone, let's just remove
it.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
@adalessandro adalessandro requested a review from kraj as a code owner December 13, 2024 15:26
@adalessandro
Copy link
Author

FYI @kraj @MaxIhlenfeldt @petermarko

@kraj
Copy link
Owner

kraj commented Dec 16, 2024

I guess you are asking to create kirkstone-clang18 branch rooted from scarthgap branch ?

@adalessandro
Copy link
Author

I guess you are asking to create kirkstone-clang18 branch rooted from scarthgap branch ?

Yes, indeed. Feedback welcome :-)

@adalessandro
Copy link
Author

@kraj let me know if that's fine or this PR needs to be amended. Thanks in advance.

@kraj
Copy link
Owner

kraj commented Dec 17, 2024

@kraj let me know if that's fine or this PR needs to be amended. Thanks in advance.

yes. I have created a new branch named kirkstone-clang18 this PR perhaps is better to be rebased on it.

@adalessandro adalessandro changed the base branch from scarthgap to kirkstone-clang18 December 17, 2024 17:22
@adalessandro
Copy link
Author

adalessandro commented Dec 17, 2024

@kraj let me know if that's fine or this PR needs to be amended. Thanks in advance.

yes. I have created a new branch named kirkstone-clang18 this PR perhaps is better to be rebased on it.

Great. Rebased and target branch changed to kirkstone-clang18.

Copy link
Owner

@kraj kraj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants