Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Earlier custom compiler path export #1072

Open
hellsgod opened this issue Jan 29, 2025 · 5 comments
Open

Earlier custom compiler path export #1072

hellsgod opened this issue Jan 29, 2025 · 5 comments

Comments

@hellsgod
Copy link

Hi.

I'm currently using clang 20 to compile the kernel and I'm playing around with some build flags. I set my custom compiler path to it, since I don't use clang 20 as system wide. When I try to use some flags, which are only available in clang 20, I can't build the kernel, since in the prepare phase the script is using the system wide compiler, which is clang 19.1.7 and I can't build with flags, which are only for clang 20. Is there a way to export the custom compiler path earlier? Right now clang 20 gets used in the build phase, but that seems to be too late.

Thank you

@ptr1337
Copy link
Collaborator

ptr1337 commented Jan 29, 2025

Hi.

I'm currently using clang 20 to compile the kernel and I'm playing around with some build flags. I set my custom compiler path to it, since I don't use clang 20 as system wide. When I try to use some flags, which are only available in clang 20, I can't build the kernel, since in the prepare phase the script is using the system wide compiler, which is clang 19.1.7 and I can't build with flags, which are only for clang 20. Is there a way to export the custom compiler path earlier? Right now clang 20 gets used in the build phase, but that seems to be too late.

Thank you

Why you just dont export the PATH to the directory of the clang installation?

@hellsgod
Copy link
Author

I've tried that. Didn't work out

@hellsgod hellsgod closed this as completed Feb 4, 2025
@AdelKS
Copy link
Collaborator

AdelKS commented Feb 4, 2025

Why did you close the issue, did you find a workaround?

@hellsgod
Copy link
Author

hellsgod commented Feb 4, 2025

An ugly one, but it worked: hellsgod@7717ade

@AdelKS AdelKS reopened this Feb 4, 2025
@AdelKS
Copy link
Collaborator

AdelKS commented Feb 4, 2025

Keeping the issue open for tracking

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

No branches or pull requests

3 participants