From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: ivecera@redhat.com
Cc: masahiroy@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
nicolas@fjasle.eu, linux-kbuild@vger.kernel.org
Subject: Can't compile v6.2-rc1 kernel rpm in openSUSE
Date: Wed, 28 Dec 2022 19:44:56 +0800 [thread overview]
Message-ID: <ee227d24-9c94-bfa3-166a-4ee6b5dfea09@linux.dev> (raw)
Hi,
With latest v6.2-rc1, I can't compile kernel rpm in openSUSE leap.
linux> make rpm-pkg -j16
SYNC include/config/auto.conf.cmd
HOSTCC scripts/kconfig/conf.o
HOSTLD scripts/kconfig/conf
UPD include/config/kernel.release
make clean
sh ./scripts/package/mkspec >./kernel.spec
TAR kernel-6.2.0_rc1_150400.24.38_default+.tar.gz
rpmbuild --target x86_64-linux -ta
kernel-6.2.0_rc1_150400.24.38_default+.tar.gz \
--define='_smp_mflags %{nil}'
Building target platforms: x86_64-linux
Building for target x86_64-linux
error: Failed build dependencies:
elfutils-libelf-devel is needed by
kernel-6.2.0_rc1_150400.24.38_default+-8.x86_64
make[1]: *** [scripts/Makefile.package:62: rpm-pkg] Error 1
make: *** [Makefile:1652: rpm-pkg] Error 2
Seems the below change in commit 8818039f959b("kbuild: add ability
to make source rpm buildable using koji") caused the issue.
@@ -49,6 +51,9 @@sed -e '/^DEL/d' -e 's/^\t*//' <<EOF
URL: https://www.kernel.org
$S Source: kernel-$__KERNELRELEASE.tar.gz
Provides: $PROVIDES
+$S BuildRequires: bc binutils bison dwarves elfutils-libelf-devel flex
+$S BuildRequires: gcc make openssl openssl-devel perl python3 rsync
Because the relevant package name in openSUSE is libelf-devel as
mentioned in ./tools/perf/Makefile.config
Please install libelf-dev, libelf-devel or elfutils-libelf-devel
Thanks,
Guoqing
reply other threads:[~2022-12-28 11:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ee227d24-9c94-bfa3-166a-4ee6b5dfea09@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=ivecera@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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;
as well as URLs for NNTP newsgroup(s).