All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.9-rc1
Date: Sun, 5 May 2024 07:01:02 +0200	[thread overview]
Message-ID: <ZjcSjk0mXYopAvVS@gmail.com> (raw)
In-Reply-To: <ZjcRPelwZP34N42s@gmail.com>


* Ingo Molnar <mingo@kernel.org> wrote:

> Notes:
> 
> - Yes, those weird 'file' and ': No such file or directory' strings are 
>   pasted as-is. No idea what it's about, and the build log doesn't say.

Forgot to mention that I also did a KBUILD_VERBOSE=2 build - which isn't 
more verbose for this particular failure:


   BTF [M] net/qrtr/qrtr.ko - due to: vmlinux
   BTF [M] net/qrtr/qrtr-smd.ko - due to: vmlinux
   BTF [M] net/qrtr/qrtr-tun.ko - due to: vmlinux
   BTF [M] net/qrtr/qrtr-mhi.ko - due to: vmlinux
 file
 : No such file or directory
 make[3]: *** [debian/rules:61: binary-image] Error 255
 dpkg-buildpackage: error: make -f debian/rules binary subprocess returned exit status 2
 make[2]: *** [scripts/Makefile.package:121: bindeb-pkg] Error 2
 make[1]: *** [/home/mingo/tip.localinstall/Makefile:1541: bindeb-pkg] Error 2
 make: *** [Makefile:240: __sub-make] Error 2
 kepler:~/tip.localinstall> 

Thanks,

	Ingo

  reply	other threads:[~2024-05-05  5:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 15:02 [GIT PULL] Kbuild updates for v6.9-rc1 Masahiro Yamada
2024-03-21 22:25 ` pr-tracker-bot
2024-05-05  4:55 ` Ingo Molnar
2024-05-05  5:01   ` Ingo Molnar [this message]
2024-05-05  5:33     ` Ingo Molnar
2024-05-05  7:26       ` Ingo Molnar
2024-05-05  8:45         ` Masahiro Yamada

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=ZjcSjk0mXYopAvVS@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.