* [PATCH] kbuild: binrpm-pkg: Propagate O= to rpmbuild
@ 2019-09-20 19:01 Jeffrey Hugo
2019-09-21 6:30 ` Masahiro Yamada
0 siblings, 1 reply; 3+ messages in thread
From: Jeffrey Hugo @ 2019-09-20 19:01 UTC (permalink / raw)
To: yamada.masahiro, michal.lkml; +Cc: linux-kbuild, linux-kernel, Jeffrey Hugo
If the user specifies O= to indicate a specific output directory for the
build, rpmbuild does not honor this, and will use its default, which could
be the user's home directory. In cases where the user has limited home
directory space, this could cause the build to outright fail.
In the case of the binrpm-pkg target, redefine the top directory for output
to be what the user specified in O=, thus the user will find a "rpmbuild"
subdirectory in that location with all of the RPM artifacts.
This does not apply to rpm-pkg, since we already cannot handle creating
the source tarball out of tree.
Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
---
scripts/Makefile.package | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/scripts/Makefile.package b/scripts/Makefile.package
index 56eadcc..aab0711 100644
--- a/scripts/Makefile.package
+++ b/scripts/Makefile.package
@@ -21,7 +21,7 @@ include $(srctree)/scripts/Kbuild.include
# - Use /. to avoid tar packing just the symlink
# Note that the rpm-pkg target cannot be used with KBUILD_OUTPUT,
-# but the binrpm-pkg target can; for some reason O= gets ignored.
+# but the binrpm-pkg target can
# Remove hyphens since they have special meaning in RPM filenames
KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE))
@@ -33,6 +33,12 @@ TAR_CONTENT := $(KBUILD_ALLDIRS) .config .scmversion Makefile \
Kbuild Kconfig COPYING $(wildcard localversion*)
MKSPEC := $(srctree)/scripts/package/mkspec
+RPM_OUTDIR :=
+ifneq ($(objtree),$(srctree))
+# Using absolute path as relative path will cause parts of rpmbuild to fail
+ RPM_OUTDIR := --define "_topdir $(abs_objtree)/rpmbuild"
+endif
+
quiet_cmd_src_tar = TAR $(2).tar.gz
cmd_src_tar = \
if test "$(objtree)" != "$(srctree)"; then \
@@ -65,8 +71,8 @@ PHONY += binrpm-pkg
binrpm-pkg:
$(MAKE) -f $(srctree)/Makefile
$(CONFIG_SHELL) $(MKSPEC) prebuilt > $(objtree)/binkernel.spec
- +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" --target \
- $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
+ +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" $(RPM_OUTDIR) \
+ --target $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
PHONY += deb-pkg
deb-pkg:
--
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] kbuild: binrpm-pkg: Propagate O= to rpmbuild
2019-09-20 19:01 [PATCH] kbuild: binrpm-pkg: Propagate O= to rpmbuild Jeffrey Hugo
@ 2019-09-21 6:30 ` Masahiro Yamada
2019-09-22 21:08 ` Jeffrey Hugo
0 siblings, 1 reply; 3+ messages in thread
From: Masahiro Yamada @ 2019-09-21 6:30 UTC (permalink / raw)
To: Jeffrey Hugo
Cc: Michal Marek, Linux Kbuild mailing list, Linux Kernel Mailing List
Hi Jeffrey,
On Sat, Sep 21, 2019 at 4:01 AM Jeffrey Hugo <jhugo@codeaurora.org> wrote:
>
> If the user specifies O= to indicate a specific output directory for the
> build, rpmbuild does not honor this, and will use its default, which could
> be the user's home directory. In cases where the user has limited home
> directory space, this could cause the build to outright fail.
>
> In the case of the binrpm-pkg target, redefine the top directory for output
> to be what the user specified in O=, thus the user will find a "rpmbuild"
> subdirectory in that location with all of the RPM artifacts.
>
> This does not apply to rpm-pkg, since we already cannot handle creating
> the source tarball out of tree.
>
> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
binrpm-pkg creates intermediate build artifacts in $(objtree)/,
but puts only the final .rpm into ${HOME}/rpmbuild/RPMS/${ARCH}/.
It has worked like that since a long time before
probably in order to respect the default of rpmbuild.
If you change this behavior, it should be consistent.
The 'rpmbuild' should be always located in the kernel tree
instead of the user's home directory.
But, doing so might give impact to other users who
rely on having 'rpmbuild' in the home directory.
I have to hear opinions from others
if this change is desired.
Meanwhile, if you are unhappy with that, one solution is to use RPMOPTS.
RPMOPTS exists to tweak the default behavior.
Thanks.
> ---
> scripts/Makefile.package | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/Makefile.package b/scripts/Makefile.package
> index 56eadcc..aab0711 100644
> --- a/scripts/Makefile.package
> +++ b/scripts/Makefile.package
> @@ -21,7 +21,7 @@ include $(srctree)/scripts/Kbuild.include
> # - Use /. to avoid tar packing just the symlink
>
> # Note that the rpm-pkg target cannot be used with KBUILD_OUTPUT,
> -# but the binrpm-pkg target can; for some reason O= gets ignored.
> +# but the binrpm-pkg target can
>
> # Remove hyphens since they have special meaning in RPM filenames
> KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE))
> @@ -33,6 +33,12 @@ TAR_CONTENT := $(KBUILD_ALLDIRS) .config .scmversion Makefile \
> Kbuild Kconfig COPYING $(wildcard localversion*)
> MKSPEC := $(srctree)/scripts/package/mkspec
>
> +RPM_OUTDIR :=
> +ifneq ($(objtree),$(srctree))
> +# Using absolute path as relative path will cause parts of rpmbuild to fail
> + RPM_OUTDIR := --define "_topdir $(abs_objtree)/rpmbuild"
> +endif
> +
> quiet_cmd_src_tar = TAR $(2).tar.gz
> cmd_src_tar = \
> if test "$(objtree)" != "$(srctree)"; then \
> @@ -65,8 +71,8 @@ PHONY += binrpm-pkg
> binrpm-pkg:
> $(MAKE) -f $(srctree)/Makefile
> $(CONFIG_SHELL) $(MKSPEC) prebuilt > $(objtree)/binkernel.spec
> - +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" --target \
> - $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
> + +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" $(RPM_OUTDIR) \
> + --target $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
>
> PHONY += deb-pkg
> deb-pkg:
> --
> Qualcomm Technologies, Inc. is a member of the
> Code Aurora Forum, a Linux Foundation Collaborative Project.
>
--
Best Regards
Masahiro Yamada
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] kbuild: binrpm-pkg: Propagate O= to rpmbuild
2019-09-21 6:30 ` Masahiro Yamada
@ 2019-09-22 21:08 ` Jeffrey Hugo
0 siblings, 0 replies; 3+ messages in thread
From: Jeffrey Hugo @ 2019-09-22 21:08 UTC (permalink / raw)
To: Masahiro Yamada
Cc: Michal Marek, Linux Kbuild mailing list, Linux Kernel Mailing List
On 9/20/2019 11:30 PM, Masahiro Yamada wrote:
> Hi Jeffrey,
>
> On Sat, Sep 21, 2019 at 4:01 AM Jeffrey Hugo <jhugo@codeaurora.org> wrote:
>>
>> If the user specifies O= to indicate a specific output directory for the
>> build, rpmbuild does not honor this, and will use its default, which could
>> be the user's home directory. In cases where the user has limited home
>> directory space, this could cause the build to outright fail.
>>
>> In the case of the binrpm-pkg target, redefine the top directory for output
>> to be what the user specified in O=, thus the user will find a "rpmbuild"
>> subdirectory in that location with all of the RPM artifacts.
>>
>> This does not apply to rpm-pkg, since we already cannot handle creating
>> the source tarball out of tree.
>>
>> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
>
>
> binrpm-pkg creates intermediate build artifacts in $(objtree)/,
> but puts only the final .rpm into ${HOME}/rpmbuild/RPMS/${ARCH}/.
I disagree with this. Ubuntu 16.04 with the 4.12 version of the rpm
packaging utilities will create several directories under rpmbuild in
the user's home directory -
BUILDROOT RPMS SOURCES SPECS SRPMS
SOURCES/SPECS/SRPMS are empty for binrpm-pkg.
RPMs contains the final RPMs as you've indicated
BUILDROOT appears to contain more intermediate files which are used to
then generate the final rpms.
It seems like more than just the final rpms are dumped into the home
directory.
>
> It has worked like that since a long time before
> probably in order to respect the default of rpmbuild.
It still seems inconsistent to me that there is an option defined
(KBUILD_OUTPUT and O=) which is described to allow the user to specify
the location of the build output, yet there are parts of the build
system which do not respect this.
I also find it curious that there is a comment in the makefile this
patch modifies that seems to suggest that it is intended for O= to
impact the binrpm-pkg target, however that is currently not the case.
>
>
> If you change this behavior, it should be consistent.
> The 'rpmbuild' should be always located in the kernel tree
> instead of the user's home directory.
I'm ok with this. The current patch attempts to preserve current
behavior in the default case of not specifying an output directory, but
dumping everything in the kernel tree seems sane to me.
>
> But, doing so might give impact to other users who
> rely on having 'rpmbuild' in the home directory.
> I have to hear opinions from others
> if this change is desired.
Fair enough.
>
> Meanwhile, if you are unhappy with that, one solution is to use RPMOPTS.
> RPMOPTS exists to tweak the default behavior.
I don't see this documented anywhere. I'm assuming that is supposed to
be an environment variable. I'll have to see how well that works with
our automated build systems. Command line options are generally preferred.
>
>
> Thanks.
>
>
>> ---
>> scripts/Makefile.package | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/scripts/Makefile.package b/scripts/Makefile.package
>> index 56eadcc..aab0711 100644
>> --- a/scripts/Makefile.package
>> +++ b/scripts/Makefile.package
>> @@ -21,7 +21,7 @@ include $(srctree)/scripts/Kbuild.include
>> # - Use /. to avoid tar packing just the symlink
>>
>> # Note that the rpm-pkg target cannot be used with KBUILD_OUTPUT,
>> -# but the binrpm-pkg target can; for some reason O= gets ignored.
>> +# but the binrpm-pkg target can
>>
>> # Remove hyphens since they have special meaning in RPM filenames
>> KERNELPATH := kernel-$(subst -,_,$(KERNELRELEASE))
>> @@ -33,6 +33,12 @@ TAR_CONTENT := $(KBUILD_ALLDIRS) .config .scmversion Makefile \
>> Kbuild Kconfig COPYING $(wildcard localversion*)
>> MKSPEC := $(srctree)/scripts/package/mkspec
>>
>> +RPM_OUTDIR :=
>> +ifneq ($(objtree),$(srctree))
>> +# Using absolute path as relative path will cause parts of rpmbuild to fail
>> + RPM_OUTDIR := --define "_topdir $(abs_objtree)/rpmbuild"
>> +endif
>> +
>> quiet_cmd_src_tar = TAR $(2).tar.gz
>> cmd_src_tar = \
>> if test "$(objtree)" != "$(srctree)"; then \
>> @@ -65,8 +71,8 @@ PHONY += binrpm-pkg
>> binrpm-pkg:
>> $(MAKE) -f $(srctree)/Makefile
>> $(CONFIG_SHELL) $(MKSPEC) prebuilt > $(objtree)/binkernel.spec
>> - +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" --target \
>> - $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
>> + +rpmbuild $(RPMOPTS) --define "_builddir $(objtree)" $(RPM_OUTDIR) \
>> + --target $(UTS_MACHINE) -bb $(objtree)/binkernel.spec
>>
>> PHONY += deb-pkg
>> deb-pkg:
>> --
>> Qualcomm Technologies, Inc. is a member of the
>> Code Aurora Forum, a Linux Foundation Collaborative Project.
>>
>
>
> --
> Best Regards
> Masahiro Yamada
>
--
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-22 21:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-20 19:01 [PATCH] kbuild: binrpm-pkg: Propagate O= to rpmbuild Jeffrey Hugo
2019-09-21 6:30 ` Masahiro Yamada
2019-09-22 21:08 ` Jeffrey Hugo
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).