Arch Linux User Repository

Repository here

@miffe

-w must be a default MAKEFLAG because removing it worked and linux-mainline installed fine.

PSA to anyone reading this: make sure -w is NOT in your makeflags, otherwise you will not be able to compile.

@SimPilotAdamT: Remove -w from MAKEFLAGS, as it will print an Entering directory... message even if -s is given.

@miffe

As a kind of update, I tried again after the new RC was released on my host machine, I tried to build linux-mainline again, and was met with the same error, with this build output from paru-git and this makepkg config file (pay attention to line 49). Any ideas?

@miffe

Do you have some weird MAKEFLAGS set?

I do have some different MAKEFLAGS specified in my makepkg.conf. They are -j20 -Wno-error -w. I still get the same errors without these set, though.

You have way too much time

eeeehhhh thing is ur probably right. At the time I found the error I already had those VM's booted up for a little test. Once I found the error in my host (running Artix), I did the same compilation in each VM, the only difference being the -j20 makeflag, each set to -j3 as those were the amounts of threads I gave to each VM to begin with.

@SimPilotAdamT:

Happens on paru, yay, and normal makepkg on Arch, Artix, Manjaro, Arco, and Garuda.

You have way to much time :)

install: cannot stat 'make: Entering directory '\''/home/adam/.cache/paru/clone/linux-mainline/src/linux-mainline'\'''$'\n''arch/x86/boot/bzImage'$'\n''make: Leaving directory '\''/home/adam/.cache/paru/clone/linux-mainline/src/linux-mainline'\''': No such file or directory

This is the real error, do you have some weird MAKEFLAGS set? On line 87 in the PKGBUILD it runs make -s image_name, -s means silent but yours still prints Entering directory ....

Fails to compile, citing warnings which I tried to disable using -Wno-error -w, but still gives those errors (I'm assuming bc of Torvalds' forcing of -Werror). The full command output is uploaded here.

Happens on paru, yay, and normal makepkg on Arch, Artix, Manjaro, Arco, and Garuda.

My PC is one I built myself, with:

Intel Core i9-10900K

MSI Ventus 3X GeForce RTX 3080 10GB GDDR6X OC

2x 16GB Corsair Vengeance RGB Pro SL DDR4-3200 CL16 DIMMs

Gigabyte Z490 AORUS Pro AX

Corsair iCue Hydro H100i RGB Pro XT

EVGA SuperNOVA 850W G2 Gold-Rated PSU

It's reasonable to use core/linux's config. I wonder if they'll enable the new filesystems in the official repos when 5.15 comes around. Especially NTFS, since it's basically THE ntfs driver now. The old one was read only.

For example, when exfat showed up in-tree, it was indeed enabled by the arch devs.

@jpegxguy: No, it's to much work. It uses the same config as core/linux. If you want a custom config you can easily change it yourself.

Hi, can you enable

CONFIG_SMB_SERVER=m

and

CONFIG_NTFS3_FS=m

for 5.15?

I don't get these kind of questions.

Please let me explain that to you; I didn't think that was too difficult to guess why I was asking for that.

This package provides a very useful way to test the newest kernel features that will land in official Arch kernels some time later. New features don't seem to get enabled by default in this config, so that's why I'm asking whether this default config in this package could include those new settings to enable the new WWAN subsystem my default. I've been testing the new WWAN subsystem for a very long time now, since the very early patches in net-next, and all the userspace tools (libmbim, libqmi, ModemManager) are ready to use that as well, even in the current official versions provided by Arch, not even AUR is needed. So, was wondering whether these settings could be included by default in this AUR package, so that everyone can benefit already from them.

The config is right there. The PKGBUILD is right there. Change it and compile it. Done.

Yes, I did that myself for my own usecase, that is not what I was asking for. Sorry if I didn't explain that clearer in my first comment.