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 06:55:25 +0200 [thread overview]
Message-ID: <ZjcRPelwZP34N42s@gmail.com> (raw)
In-Reply-To: <CAK7LNARXef6Myb_Gd4jyGfwujoBAjmjzLZBzgkm4T1KmfHP0MQ@mail.gmail.com>
* Masahiro Yamada <masahiroy@kernel.org> wrote:
> kbuild: simplify dtbs_install by reading the list of compiled DTBs
> kbuild: deb-pkg: show verbose log for direct package builds
> kbuild: deb-pkg: make debian/rules quiet for 'make deb-pkg'
> kbuild: deb-pkg: build binary-arch in parallel
> kbuild: deb-pkg: call more misc debhelper commands
> kbuild: rpm-pkg: do not include depmod-generated files
> kbuild: rpm-pkg: mark installed files in /boot as %ghost
Not sure whether it's related to these commits, but the kernel package
build on Ubuntu is broken currently - both the deb-pkg and bindeb-pkg
targets result in this build failure:
$ make -j32 deb-pkg
...
BTF [M] net/qrtr/qrtr-mhi.ko
BTF [M] net/qrtr/qrtr-tun.ko
BTF [M] net/batman-adv/batman-adv.ko
BTF [M] net/sctp/sctp.ko
BTF [M] net/mac80211/mac80211.ko
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: deb-pkg] Error 2
make[1]: *** [/home/mingo/tip.localinstall/Makefile:1541: deb-pkg] Error 2
make: *** [Makefile:240: __sub-make] Error 2
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.
- The .config is an unremarkable .config derived from Ubuntu's own kernel
config - can send it separately to you if it matters.
- Software version is Ununtu 23.10 with the latest updates. Can send
details if it matters. Is there an easy Make command to run to extract
the software versions you'd need, instead of having to manually extract
it from a zillion tools and packages? 'make build-environment' or so?
- The kernel package build is also incredibly slow, as reported by others
back in January AFAICS, which makes bisection impractical. There's no
other build failure visible in the build log.
I did one strace of the build (which is even more incredibly slow, takes
about an hour literally on a 4GHz box with 64 CPUs), which has shown this
weird instance shortly before the failure:
3027593 newfstatat(AT_FDCWD, "deb-pkg", 0x7ffeef9f9960, 0) = -1 ENOENT (No such file or directory)
... which might or might not be normal Make behavior.
Thanks,
Ingo
next prev parent reply other threads:[~2024-05-05 4:55 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 [this message]
2024-05-05 5:01 ` Ingo Molnar
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=ZjcRPelwZP34N42s@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox