From: Kyle Pelton <kyle.d.pelton@linux.intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Subject: make rpm-pkg broken after f8d94c4e403c kbuild: do not create intermediate...
Date: Tue, 18 Apr 2023 14:48:06 -0700 [thread overview]
Message-ID: <ZD8Py7WsKLK3umvX@kdpelton-desk> (raw)
Hello,
I am getting the below rpm-pkg build failure after this patch was
introduced in v6.2-rc7:
f8d94c4e403c kbuild: do not create intermediate *.tar for source tarballs
If I revert the patch, the failure is gone.
Thanks,
Kyle
f8d94c4e403c kbuild: do not create intermediate *.tar for source tarballs
[root@efd6e5b39c41 linux]# RPMOPTS="--nodeps" make rpm-pkg
sh ./scripts/package/mkspec >./kernel.spec
rpmbuild --nodeps --target x86_64-linux -bs kernel.spec \
--define='_smp_mflags %{nil}' --define='_sourcedir rpmbuild/SOURCES' --define='_srcrpmdir .'
Building target platforms: x86_64-linux
Building for target x86_64-linux
Wrote: ./kernel-6.3.0_rc7_00043_gaf67688dca57-1.src.rpm
rpmbuild --nodeps --target x86_64-linux -rb kernel-6.3.0_rc7_00043_gaf67688dca57-1.src.rpm \
--define='_smp_mflags %{nil}'
Installing kernel-6.3.0_rc7_00043_gaf67688dca57-1.src.rpm
Building target platforms: x86_64-linux
Building for target x86_64-linux
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Pa04vf
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd /root/rpmbuild/BUILD
+ rm -rf linux
+ /usr/bin/gzip -dc /root/rpmbuild/SOURCES/linux.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd linux
/var/tmp/rpm-tmp.Pa04vf: line 40: cd: linux: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.Pa04vf (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.Pa04vf (%prep)
make[1]: *** [scripts/Makefile.package:69: rpm-pkg] Error 1
make: *** [Makefile:1656: rpm-pkg] Error 2
reply other threads:[~2023-04-18 21:48 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=ZD8Py7WsKLK3umvX@kdpelton-desk \
--to=kyle.d.pelton@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.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.