Search Criteria
Package Details: linux-ck-headers 6.11.10-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Package Base: | linux-ck |
Description: | Headers and scripts for building modules for Linux-ck kernel |
Upstream URL: | https://wiki.archlinux.org/index.php/Linux-ck |
Licenses: | GPL-2.0-only |
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 459 |
Popularity: | 0.137884 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2024-11-26 13:15 (UTC) |
Dependencies (11)
- linux-ckAUR
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- xz (xz-gitAUR) (make)
Required by (8)
- ch343-dkms (optional)
- ch343ser-dkms-git (optional)
- ch9344ser-dkms-git (optional)
- e1000e-dkms (optional)
- fl2000-dkms (optional)
- i2c-ch341-dkms (optional)
- igb-dkms (optional)
- spi-config-dkms (optional)
Latest Comments
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 308 Next › Last »
graysky commented on 2019-08-28 18:41 (UTC)
@air-g4p - I do not use ccache so I cannot comment. I will say that builds using distcc on 5.2 fail where they worked fine with 5.1. Related? The change in the chroot build might be due to the modprobed-db change I made wherein the old behavior was to call it in recall mode via sudo which was always hacky in a PKGBUILD. The current method reads the database directly which the build scripts might not allow since your homedir is outside of the build root. Try building in the chroot without using the modprobed-db enabled; that will probably work.
air-g4p commented on 2019-08-28 13:08 (UTC)
@graysky - built without issue with ccache disabled, while running
makepkg -sri
so what is driving that fail?Also, why did -ck previously build (many times) without issue in a clean chroot, but now it fails?
Thanks...
graysky commented on 2019-08-27 19:09 (UTC)
@air-g4p - Disable ccache and try again
air-g4p commented on 2019-08-27 08:25 (UTC) (edited on 2019-08-27 12:34 (UTC) by air-g4p)
@graysky,
In a clean folder, and running
makepkg -sri
the build failed, but in a different way. I got as far as:-> Applying patch 0004-drm-amdgpu-pin-the-csb-buffer-on-hw-init-for-gfx-v8.patch... patching file drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c -> Setting config... -> Applying enable_additional_cpu_optimizations_for_gcc_v9.1+_kernel_v4.13+.patch ... patching file arch/x86/include/asm/module.h patching file arch/x86/Kconfig.cpu patching file arch/x86/Makefile patching file arch/x86/Makefile_32.cpu HOSTCC scripts/basic/fixdep /usr/bin/ccache: invalid option -- 'W'
then I also saw:
make[1]: [scripts/Makefile.host:90: scripts/basic/fixdep] Error 1 make: [Makefile:508: scripts_basic] Error 2 ==> ERROR: A failure occurred in prepare(). Aborting...
Any ideas? Thanks
graysky commented on 2019-08-26 21:05 (UTC)
@air-g4p - Does it build outside of the chroot? I'm thinking the chroot build script doesn't look outside of that environment and will therefore fail.
air-g4p commented on 2019-08-26 16:51 (UTC)
@graysky,
I'm seeing several inexplicable errors with the latest build:
When trying to build ck with
time extra-x86_64-build
in a clean chroot, I get as far as:Kernel Live Patching (LIVEPATCH) [N/y/?] n
configuration written to .config
-> No modprobed.db data found /startdir/PKGBUILD: line 157: exit1: command not found ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/user/build
this DESPITE: modprobed-db store showing:
180 modules currently loaded per /proc/modules 180 modules are in /home/user/.config/modprobed.db
AND the correct path in PKGBUILD:
_localmodcfg=/home/user/.config/modprobed.db
Also, please have a look at Line 157 of PKGBUILD.
Did you intend to type
exit
as opposed to your currentexit1
?I have never seen this modprobed error previously.
Ideas are welcome...
graysky commented on 2019-08-20 19:31 (UTC)
I haven't made an ISO/no idea. You could ask on CK's blog why it fails with that mount command. I do not edit beyond the changes his patchset make.
zerophase commented on 2019-08-20 00:46 (UTC)
@graysky archiso failing to build appears to be an issue with the CK kernel. No, idea what's different from Arch, as the only thing I changed was the compression algorithm used for initramfs.
Have any idea what might be causing the mount failure with CK?
https://bugs.archlinux.org/task/63508
zerophase commented on 2019-08-17 18:41 (UTC)
@graysky This is a forum post I made on the issue. It looks like folders under the work directory are not able to be identified as mount points. If you install archiso, and just run
sudo cp -r /usr/share/archiso/configs/releng/ ~/archlive; cd ~/archlive; sudo ./build.sh -v
The issue should reproduce itself.I just happened to decide to try the Arch kernel to see if that resolved the build failure I was receiving, and everything just built successfully. Looks like others have identified this issue in the past, but did not report it. I have a feeling it has something to do with
mkarchiso
.https://bbs.archlinux.org/viewtopic.php?id=248473
https://unix.stackexchange.com/questions/460043/how-can-i-successfully-build-an-archiso-image-airootfs-is-not-a-mountpoint
graysky commented on 2019-08-17 11:10 (UTC)
You have provided nothing to go on...
« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 308 Next › Last »