public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Jim Davis <jim.epost@gmail.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/package/Makefile: rpmbuild is needed for rpm targets
Date: Mon, 15 Jun 2015 16:12:43 +0200	[thread overview]
Message-ID: <557EDD5B.5050703@suse.cz> (raw)
In-Reply-To: <1433794748-6570-1-git-send-email-jim.epost@gmail.com>

On 2015-06-08 22:19, Jim Davis wrote:
> Before rpm release 4.1, in 2002, either the rpm command or the
> rpmbuild command could be used in the rpm-pkg or binrpm-pkg targets,
> and the Makefile chose the rpm command if the rpmbuild command wasn't
> found.
> 
> After release 4.1, however, the rpm command could no longer be used in
> place of the rpmbuild command.  As the rpmbuild command is not
> installed by default, this can lead to failures with the rpm-pkg and
> binrpm-pkg targets:
> 
> rpm --define "_builddir ." --target \
>     x86_64 -bb ./binkernel.spec
>     rpm --target: unknown option
>     scripts/package/Makefile:60: recipe for target 'binrpm-pkg' failed
> 
> Change the Makefile to use rpmbuild unconditionally to avoid this.
> 
> Signed-off-by: Jim Davis <jim.epost@gmail.com>

I agree that compatibility with rpm < 4.1 is not an issue nowadays and
"rpmbuild: command not found" is a lot more informative error message. I
applied the patch to kbuild.git#misc.

thanks,
Michal


      reply	other threads:[~2015-06-15 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+r1ZhiyQbakrxr4saPE_mFjwjGG4aJxLHm3oCvqD=4=ByBA_w@mail.gmail.com>
2015-06-08 20:19 ` [PATCH] scripts/package/Makefile: rpmbuild is needed for rpm targets Jim Davis
2015-06-15 14:12   ` Michal Marek [this message]

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=557EDD5B.5050703@suse.cz \
    --to=mmarek@suse.cz \
    --cc=jim.epost@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox