You are not logged in.
Both the linux and linux-ck PKGBUILDs work with the config they supply. The change you make to the config makes the build fail. Making it your issue.
Offline
the point is that you have to edit the kernel config for the PKGBUILD and thus the compilation to fail.
by changing the config the resulting kernel would be unsupported.
thus this packagebuild would be unsupported too.
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
nvm didn't see the second page and wondered why my message disappeared
Last edited by jl2 (2023-07-30 15:25:36)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
Both the linux and linux-ck PKGBUILDs work with the config they supply
All right, now it's clear. BTW, I just thought these lines could improve the PKGBUILD.
However, for me (at least) the problem is solved, if everybody agree I'd add the 'SOLVED' in the title
Offline
Yeah, mark it solved, also fixed here.
They well also improve my PKGBUILDs, too
Last edited by jl2 (2023-07-31 06:18:21)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
loqs wrote:Both the linux and linux-ck PKGBUILDs work with the config they supply
All right, now it's clear. BTW, I just thought these lines could improve the PKGBUILD.
However, for me (at least) the problem is solved, if everybody agree I'd add the 'SOLVED' in the title
Sure.
I think the cause of the issue could have been located sooner if you had mentioned the changes you made to the config in your first post.
If you want linux-ck modified I would suggest contacting graysky.
Offline