Package Base Details: linux-ck

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 461
Popularity: 1.12
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-03-16 18:02 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 305 Next › Last »

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 build

brunomiguel 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 the env 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

VGrol commented on 2022-12-01 02:42 (UTC) (edited on 2022-12-01 06:33 (UTC) by VGrol)

I'm also having the same issues as Air-G4P, with Nvidia-DKMS failing after having successfully built and installed linux-ck, linux-ck-headers, both via AUR helper and manually with makepkg.

Identical error of resolve_btfids

After some research, I found a solution, posted by Logs, on the Linux-CK thread on the BBS forums. It can be resolved by uncommenting the following line in the PKGBUILD.

air-g4p commented on 2022-10-09 14:41 (UTC)

@graysky - Thank you for your suggestion.

If I understood you correctly, I did copy my modprobed.db to my build directory containing the 6.0-1 PKGBUILD, added that file to the source array, appended the 256sum and modified the make line to the statement you referenced below.

The PKGBUILD I used is here: http://ix.io/4cFF

The only relevant modifications I made were on lines: 97, 111 and 194.

The build did succeed, without any reported error. However I still suspect time makechrootpkg -c -r $CHROOT is silently ignoring the reading/use of the 'modprobed.db' file as my build time still exceeded 5.5+ hours and my ~/chroot/user folder is (again) 20 GiB.

If you had another build process idea in mind, please let me know.

Cheers

graysky commented on 2022-10-07 10:06 (UTC)

I think you will have to copy the file into the chroot. By design it shouldn't be able to read outside. Why not just copy the database into the same dir as the PKGBUILD, and include it in the source array. Change the line like this to call it:

make LLVM=$_LLVM LLVM_IAS=$_LLVM LSMOD="../modprobed.db" localmodconfig

air-g4p commented on 2022-10-07 07:11 (UTC)

@graysky - 5.19.14-1 built and 'dkms install' completed without error, but only when building in a clean chroot using makechrootpkg -c -r $CHROOT.

The chroot build fails unless _localmodcfg= is left empty, which of course, causes very long build times.

Is there any way to force the chroot to use _localmodcfg=/home/<userID>/.config/modprobed.db?

Cheers

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 305 Next › Last »