Package Details: linux-next-git 20240529.r0.g9d99040b1bc8-1

Git Clone URL: https://aur.archlinux.org/linux-next-git.git (read-only, click to copy)
Package Base: linux-next-git
Description: The Linux NEXT kernel and modules
Upstream URL: http://www.kernel.org/
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: Nefelim4ag
Maintainer: sir_lucjan (ptr1337)
Last Packager: sir_lucjan
Votes: 17
Popularity: 0.002675
First Submitted: 2014-10-12 19:04 (UTC)
Last Updated: 2024-05-30 09:23 (UTC)

Dependencies (15)

Required by (7)

Sources (4)

Latest Comments

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

sir_lucjan commented on 2023-01-31 20:32 (UTC)

@riod

This solution works very well if you want to disable DEBUG in the kernel. If you leave it on by default, you won't notice any difference in the build. In my kernels I mostly use this solution and I have not had any error report. I am glad that after much perturbation I was able to solve the problem. Thanks for the notification and feedback.

olean commented on 2023-01-31 20:29 (UTC)

i don't know enough about btf to say whether your modification is a good idea or not. so really it's up to you

sir_lucjan commented on 2023-01-31 20:24 (UTC) (edited on 2023-01-31 20:24 (UTC) by sir_lucjan)

@riod

If you want, I could add something like this:

# required when DEBUG_INFO_BTF_MODULES is enabled
  if [ -f tools/bpf/resolve_btfids/resolve_btfids ]; then
        install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids
  fi

sir_lucjan commented on 2023-01-31 20:21 (UTC) (edited on 2023-01-31 20:22 (UTC) by sir_lucjan)

@riod

So the current solution can be considered as working?

olean commented on 2023-01-31 20:11 (UTC)

pulling the latest version i was able to build after disabling btf

sir_lucjan commented on 2023-01-31 18:37 (UTC)

@riod

Could you check now?

sir_lucjan commented on 2023-01-31 17:12 (UTC)

This is a temporary solution, once selected it should work properly. I will try to find a more convenient option soon.

olean commented on 2023-01-31 17:07 (UTC)

i'm now seeing this :

.config:7730:warning: symbol value 'm' invalid for USB_FOTG210_HCD .config:7967:warning: symbol value 'm' invalid for USB_FOTG210_UDC .config:8559:warning: symbol value 'm' invalid for VFIO_VIRQFD

and then it starts asking for manual selection for new config options

sir_lucjan commented on 2023-01-31 15:37 (UTC)

Could you check the latest update?

sir_lucjan commented on 2023-01-31 15:32 (UTC)

No, it probably doesn't work either. I need to find a solution.

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