From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Masahiro Yamada <masahiroy@kernel.org>, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Ivan Vecera" <ivecera@redhat.com>,
"Jonathan Toppins" <jtoppins@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Íñigo Huguet" <ihuguet@redhat.com>
Subject: Re: [PATCH] kbuild: rpm-pkg: add libelf-devel as alternative for BuildRequires
Date: Thu, 29 Dec 2022 10:08:18 +0800 [thread overview]
Message-ID: <ce9e05f5-4752-7f70-9355-da881565b96c@linux.dev> (raw)
In-Reply-To: <20221228191014.659746-1-masahiroy@kernel.org>
On 12/29/22 03:10, Masahiro Yamada wrote:
> Guoqing Jiang reports that openSUSE cannot compile the kernel rpm due
> to "BuildRequires: elfutils-libelf-devel" added by commit 8818039f959b
> ("kbuild: add ability to make source rpm buildable using koji").
> The relevant package name in openSUSE is libelf-devel.
>
> Add it an alternative package.
>
> BTW, if it is impossible to solve the build requirement, the final
> resort would be:
>
> $ make RPMOPTS=--nodeps rpm-pkg
>
> This passes --nodeps to the rpmbuild command so it will not verify
> build dependencies. This is useful to test rpm builds on non-rpm
> system. On Debian/Ubuntu, for example, you can install rpmbuild by
> 'apt-get install rpm'.
>
> NOTE1:
> Likewise, it is possible to bypass the build dependency check for
> debian package builds:
>
> $ make DPKG_FLAGS=-d deb-pkg
>
> NOTE2:
> The 'or' operator is supported since RPM 4.13. So, old distros such
> as CentOS 7 will break. I suggest installing newer rpmbuild in such
> cases.
>
> Link: https://lore.kernel.org/linux-kbuild/ee227d24-9c94-bfa3-166a-4ee6b5dfea09@linux.dev/T/#u
> Fixes: 8818039f959b ("kbuild: add ability to make source rpm buildable using koji")
> Reported-by: Guoqing Jiang <guoqing.jiang@linux.dev>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> scripts/package/mkspec | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/package/mkspec b/scripts/package/mkspec
> index dda00a948a01..adab28fa7f89 100755
> --- a/scripts/package/mkspec
> +++ b/scripts/package/mkspec
> @@ -51,7 +51,8 @@ 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: bc binutils bison dwarves
> +$S BuildRequires: (elfutils-libelf-devel or libelf-devel) flex
> $S BuildRequires: gcc make openssl openssl-devel perl python3 rsync
>
> # $UTS_MACHINE as a fallback of _arch in case
Thanks for the quick fix! I verified the above works for openSUSE leap 15.4.
Tested-by: Guoqing Jiang <guoqing.jiang@linux.dev>
Thanks,
Guoqing
next prev parent reply other threads:[~2022-12-29 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 19:10 [PATCH] kbuild: rpm-pkg: add libelf-devel as alternative for BuildRequires Masahiro Yamada
2022-12-29 0:26 ` Nathan Chancellor
2022-12-29 2:08 ` Guoqing Jiang [this message]
2022-12-29 8:08 ` Jonathan Toppins
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=ce9e05f5-4752-7f70-9355-da881565b96c@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=agordeev@linux.ibm.com \
--cc=ihuguet@redhat.com \
--cc=ivecera@redhat.com \
--cc=jtoppins@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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