[SOLVED] Makefile fails while compiling linux-5.15.88-gentoo

[EmDeeTee]

Hi. I've downloaded the new stable gentoo-sources (5.15.88), created a symlink using eselect kernel, but when I try to `make` it shows me this:

Code: Select all

hell /usr/src/linux # make
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND objtool
  CHK     include/generated/compile.h
arch/x86/entry/vdso/Makefile:206: *** target pattern contains no '%'.  Stop.
make[2]: *** [scripts/Makefile.build:552: arch/x86/entry/vdso] Error 2
make[1]: *** [scripts/Makefile.build:552: arch/x86/entry] Error 2
make: *** [Makefile:1902: arch/x86] Error 2

[turtles]

Hi. I've downloaded the new stable gentoo-sources (5.15.88), created a symlink using eselect kernel, but when I try to `make` it shows me this:

Code: Select all

hell /usr/src/linux # make
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND objtool
  CHK     include/generated/compile.h
arch/x86/entry/vdso/Makefile:206: *** target pattern contains no '%'.  Stop.
make[2]: *** [scripts/Makefile.build:552: arch/x86/entry/vdso] Error 2
make[1]: *** [scripts/Makefile.build:552: arch/x86/entry] Error 2
make: *** [Makefile:1902: arch/x86] Error 2

did you first run

Code: Select all

make menuconfig

and configure the kernel ?

[logrusx]

Check with the wiki if you've missed something.

Best Regards,
Georgi

[luna80]

did you copy the .config of the old kernel in the new kernel directory?

and, if yes, did you do

Code: Select all

#make oldconfig

if yes, try

Code: Select all

#make clean

and after retry with make

[EmDeeTee]

did you copy the .config of the old kernel in the new kernel directory?

and, if yes, did you do

Code: Select all

#make oldconfig

if yes, try

Code: Select all

#make clean

and after retry with make

Thank you for responding. Yes, I've followed the wiki, and yes I've tried doing `make oldconfig` and `make clean`, but every time I invoke make it shows that error

Could that be a problem in the Linux kernel makefile? There is no way, right?

[EmDeeTee]

Hi. I've downloaded the new stable gentoo-sources (5.15.88), created a symlink using eselect kernel, but when I try to `make` it shows me this:

Code: Select all

hell /usr/src/linux # make
  CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND objtool
  CHK     include/generated/compile.h
arch/x86/entry/vdso/Makefile:206: *** target pattern contains no '%'.  Stop.
make[2]: *** [scripts/Makefile.build:552: arch/x86/entry/vdso] Error 2
make[1]: *** [scripts/Makefile.build:552: arch/x86/entry] Error 2
make: *** [Makefile:1902: arch/x86] Error 2

did you first run

Code: Select all

make menuconfig

and configure the kernel ?

Yes, I've copied my old .config, ran `make oldconfig` and verified it with `make menuconfig`

[Hu]

Code: Select all

hell /usr/src/linux # make
arch/x86/entry/vdso/Makefile:206: *** target pattern contains no '%'.  Stop.
make[2]: *** [scripts/Makefile.build:552: arch/x86/entry/vdso] Error 2

What is the content of that line? What are the current values of any variables that line references? Some users may not have that specific source version installed, and so cannot check locally.

[EmDeeTee]

Code: Select all

hell /usr/src/linux # make
arch/x86/entry/vdso/Makefile:206: *** target pattern contains no '%'.  Stop.
make[2]: *** [scripts/Makefile.build:552: arch/x86/entry/vdso] Error 2

What is the content of that line? What are the current values of any variables that line references? Some users may not have that specific source version installed, and so cannot check locally.

This is the line 206

Code: Select all

$(MODLIB)/vdso: FORCE

Code: Select all

$(MODLIB)/vdso: FORCE
        @mkdir -p $(MODLIB)/vdso

[Hu]

That matches what I expect from the kernel sources, so no Gentoo patches have moved it. I also asked about the current values of those variables. What does MODLIB expand to?

[EmDeeTee]

That matches what I expect from the kernel sources, so no Gentoo patches have moved it. I also asked about the current values of those variables. What does MODLIB expand to?

In the main Makefile I've found this:

Code: Select all

#
# INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
# relocations required by build roots.  This is not defined in the
# makefile but the argument can be passed to make if needed.
#

MODLIB  = $(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE)
export MODLIB

[Hu]

That is the basic definition of MODLIB, before recursive expansion. To what string does MODLIB evaluate after expanding the contained variables, recursively? Answering that requires at least INSTALL_MOD_PATH and KERNELRELEASE, and may require more if either of those is itself a variable reference. Per the comment, INSTALL_MOD_PATH defaults to undefined, but if it is set in your process environment, that would take precedence over the default empty string.

[logrusx]

Are you sure you emerged gentoo-sources and not gentoo-kernel?

What does `equery list sys-kernel/*` say?
It might be good to also post what `eselect kernel list` say.

Best Regards,
Georgi

[turtles]

EmDeeTee I think what hu is asking is for you to edit the Makefile and add a info line right below the line

Code: Select all

export MODLIB

like so:

Code: Select all

export MODLIB
$(info "MODLIB $(MODLIB)")

Then when you run make it will print out the value of MODLIB
Like so

make
"MODLIB /lib/modules/5.16.14-gentoo"
CC arch/x86/kernel/asm-offsets.s
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh

[sublogic]

I'll chip in another idea.

Code: Select all

# make V=1

to increase verbosity, or even

Code: Select all

# script -c 'make V=1'

to capture the output in a "typescript" file. Maybe you'll get a more informative error message. Or maybe not, but it's easy enough to try.

[EmDeeTee]

Thank you everybody so much for tips and suggestions on how I could fix my problem, but I managed to figure it out on my own.

Turns out, that I had a semicolon in General Setup -> Local Version.

This is what caused the Makefile to fail

[Hu]

scripts/setlocalversion will be run by Makefile to generate include/config/kernel.release, and will write the value of CONFIG_LOCALVERSION to that file, if set. In turn, Makefile will load the content of that file into the Make variable KERNELRELEASE, which becomes an input to the variable MODLIB. Putting a semicolon in CONFIG_LOCALVERSION allowed that to enter KERNELRELEASE, which confused Make when that was expanded raw. To fix this, the value loaded into KERNELRELEASE would need to be backslash-escaped, or the expansion of it could be escaped at expansion time. Either way, this may expose more bugs, since that would put a semicolon in a directory name, and some tools may not handle that well.

[turtles]

scripts/setlocalversion will be run by...../snip//.. and some tools may not handle that well.

Hu whenever you join a thread I yell "Hu is in the house!" at my screen.
Same with Neddy.