Search Criteria
Package Details: linux-next-git-headers 20210219.r0.gabaf6f60176f-1
Git Clone URL: | https://aur.archlinux.org/linux-next-git.git (read-only, click to copy) |
---|---|
Package Base: | linux-next-git |
Description: | Headers and scripts for building modules for the Linux NEXT kernel |
Upstream URL: | http://www.kernel.org/ |
Licenses: | |
Submitter: | Nefelim4ag |
Maintainer: | sir_lucjan |
Last Packager: | sir_lucjan |
Votes: | 14 |
Popularity: | 0.34 |
First Submitted: | 2014-10-12 19:04 |
Last Updated: | 2021-02-19 18:15 |
Dependencies (15)
- linux-next-git
- pahole (pahole-git)
- bc (bc-gh) (make)
- cpio (cpio-git) (make)
- git (git-git) (make)
- graphviz (make)
- imagemagick (graphicsmagick-imagemagick-compat, imagemagick-no-hdri, imagemagick-git, imagemagick-full, imagemagick-full-git, imagemagick-fftw) (make)
- kmod (kmod-nc, kmod-git, kmod-minimal-git) (make)
- libelf (elfutils-git, libelf-minimal-git) (make)
- pahole (pahole-git) (make)
- perl (perl-git) (make)
- python-sphinx (python-sphinx-git, python-sphinx-2) (make)
- python-sphinx_rtd_theme (make)
- tar (tar-libarchive, tar-git, tar-parallel) (make)
- xz (xz-git, xz-static-git) (make)
Required by (0)
Sources (4)
- config
- git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- https://gitlab.com/sirlucjan/kernel-patches/raw/master/5.11/arch-patches-v2/0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch
- https://gitlab.com/sirlucjan/kernel-patches/raw/master/5.11/docs-patches/0001-Documentation-Fix-sphinx-3.5-causes-compilation-erro.patch
Latest Comments
1 2 3 4 5 6 ... Next › Last »
Ttz_ztT commented on 2021-01-12 16:45
@habys : same here. builds fine, doesn't want to boot. with an almost identical entry for /boot (nvme0n1p1 instead) on booting kernel.
dmesg gives lots of "BPF:No data" and "failed to validate module [crc*] BTF: -22" ?
The only difference I see in dmesg is that -next finds a numa node on my ryzen 3xxx now...
Edit: 210115 works.
habys commented on 2021-01-09 16:39
This is building for me. Anyone else having their system die as I can't manage to mount /boot? (wrong fs type, bad option, bad superblock).
From my working kernel I see: /dev/nvme1n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
eggz commented on 2020-12-07 01:46
confirmed for my part (rc7). revert that commit and the (upstream) kernels wil build. Lets hope upstream will wake up to this soon.
sir_lucjan commented on 2020-12-06 23:41
I suspect that this is the culprit.
https://github.com/torvalds/linux/commit/3351b16af4946fff0d46481d155fb91adb28b1
eggz commented on 2020-12-06 23:36
Looks like upstream has done nothing yet. This error is now also present in linux v5.10-rc7
sir_lucjan commented on 2020-12-06 21:58
@bennebartsch
If this is not a problem, I would ask you to read the previous comments and draw the appropriate conclusion from it.
Thank you.
bennebartsch commented on 2020-12-06 21:55
FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...
sir_lucjan commented on 2020-12-01 14:50
@ekollof
NOT out-of-date!
This is not a packaging error. Report it in upstream and do not mark a package as out of date.
Bednar commented on 2020-11-26 11:40
Hi @sir_lucjan
Thanks, I resolved the below with a clean build.
Now I am getting this:
FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...
Anyone else?
sir_lucjan commented on 2020-10-15 19:13
I can not confirm: