Search Criteria
Package Base Details: linux-ck
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 452 |
Popularity: | 2.98 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2023-01-26 13:05 (UTC) |
Latest Comments
1 2 3 4 5 6 .. 303 Next › Last »
VGrol commented on 2022-12-05 03:43 (UTC)
I've been tinkering with some custom patches for this package, but what would be the best way to automate the build process, in particular; How do I prevent the half a dozen prompts for drivers, like (GPIO_BT8XX)?
I'm a bit of a novice when it comes to this, so some help would be appreciated!
brunomiguel commented on 2022-12-04 22:16 (UTC)
I appreciate your feedback, and I'll look into the snippet you shared so I can integrate it into my build system. Thank you!! 😊
graysky commented on 2022-12-04 21:17 (UTC)
What you're proposing is too non-standard for most other users IMO. If you can tweak your build script that would be preferable for your edge use case.
For my build script, the strategy is to first make the set of PKGBUILD files needed for the 4 subarches then copy them into a working dir to build. You might try something like that.
brunomiguel commented on 2022-12-04 20:53 (UTC)
Editing the file makes it harder for automated builds, and it's trivial to add those entries as environment variables on the PKGBUILD. I understand you are not obligated to do so; you have it this way, and anyone who wants it differently can fork it, just like with any other FOSS project.
To make it easy for automated builds, would you be willing to use environment variables on the PKGBUILD to choose the sub-architecture and the compiler?
Thank you for creating the PKGBUILD for this kernel 🤝
artafinde commented on 2022-12-04 09:49 (UTC)
graysky: after the change for
resolve_btfids
issue below can you build the generic in a clean chroot?graysky commented on 2022-12-04 09:38 (UTC)
Works fine as-is for me. Edit the PKGBUILD defining a valid number for
_subarch=
and buildbrunomiguel commented on 2022-12-03 18:23 (UTC) (edited on 2022-12-03 19:26 (UTC) by brunomiguel)
Could you enable passing the
_subarch
variable with a value to the build process? I've been trying to pass it, either exporting it beforehand or using theenv
command, but it always requires user input. This prevents me from automating the build process for this kernel.A way to fix it is changing
_subarch=
to"${_subarch:=""}"
when first declaring it.graysky commented on 2022-12-01 08:01 (UTC)
Fixed in -3
1 2 3 4 5 6 .. 303 Next › Last »