public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org, Nicolas Schier <nsc@kernel.org>
Subject: Re: linux-next: new objtool warnings
Date: Wed, 5 Nov 2025 20:16:13 +0100	[thread overview]
Message-ID: <20251105191613.GA1831451@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251105170715.GA706366@ax162>

On Wed, Nov 05, 2025 at 10:07:15AM -0700, Nathan Chancellor wrote:

>   $ make -skj"$(nproc)" ARCH=x86_64 vmlinux.o
>   Makefile:1912: warning: overriding recipe for target 'vmlinux.o'
>   Makefile:1150: warning: ignoring old recipe for target 'vmlinux.o'
>   make[2]: *** No rule to make target 'vmlinux.o'.
> 
> When did this work? 

Dunno, I have vague memories of it working. The only reason I tried
is that vmlinux seems to be misbehaving.

> As for the second comment, if I build the vmlinux target, I see:
> 
>   AR      built-in.a
>   AR      vmlinux.a
>   LD      vmlinux.o
>   MODPOST vmlinux.symvers
>   CC      .vmlinux.export.o
>   UPD     include/generated/utsversion.h
>   CC      init/version-timestamp.o
>   KSYMS   .tmp_vmlinux0.kallsyms.S
>   AS      .tmp_vmlinux0.kallsyms.o
>   LD      .tmp_vmlinux1
>   NM      .tmp_vmlinux1.syms
>   KSYMS   .tmp_vmlinux1.kallsyms.S
>   AS      .tmp_vmlinux1.kallsyms.o
>   LD      .tmp_vmlinux2
>   NM      .tmp_vmlinux2.syms
>   KSYMS   .tmp_vmlinux2.kallsyms.S
>   AS      .tmp_vmlinux2.kallsyms.o
>   LD      vmlinux.unstripped
>   NM      System.map
>   SORTTAB vmlinux.unstripped
>   OBJCOPY vmlinux
>   OBJCOPY modules.builtin.modinfo
>   GEN     modules.builtin

# make O=tmp-build clean
# make O=tmp-build allmodconfig
# make O=tmp-build -j64 vmlinux 2>&1 | grep "\[M\]"
  CC [M]  sound/sound_core.o
  CC [M]  virt/lib/irqbypass.o
  AS [M]  arch/x86/crypto/twofish-x86_64-asm_64.o
  CC [M]  arch/x86/crypto/twofish_glue.o
  CC [M]  samples/vfio-mdev/mtty.o
  CC [M]  sound/ac97_bus.o
  AS [M]  arch/x86/crypto/twofish-x86_64-asm_64-3way.o
  CC [M]  arch/x86/crypto/twofish_glue_3way.o

  reply	other threads:[~2025-11-05 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  0:15 linux-next: new objtool warnings Stephen Rothwell
2025-11-03  9:10 ` Peter Zijlstra
2025-11-03  9:32   ` Stephen Rothwell
2025-11-03  9:38     ` Peter Zijlstra
2025-11-05  3:30       ` Stephen Rothwell
2025-11-05  8:56         ` Peter Zijlstra
2025-11-05 10:00           ` Peter Zijlstra
2025-11-05 10:02             ` Peter Zijlstra
2025-11-05 10:10               ` Peter Zijlstra
2025-11-05 17:07                 ` Nathan Chancellor
2025-11-05 19:16                   ` Peter Zijlstra [this message]
2025-11-05 20:09                     ` Nathan Chancellor
2025-11-06 11:48                       ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251105191613.GA1831451@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox