From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yu Chen <yu.chen.surf@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Error when building the kernel on top of 4.14-rc1 for target firmware_install?
Date: Wed, 20 Sep 2017 07:37:50 +0200 [thread overview]
Message-ID: <20170920053750.GA29160@kroah.com> (raw)
In-Reply-To: <CADjb_WRwQhmvEBuCKSDkAcytkHOK8gqevSrSuVAWR-ecvH1gaw@mail.gmail.com>
On Wed, Sep 20, 2017 at 11:20:19AM +0800, Yu Chen wrote:
> Hi,
> kernel compile failed after running # make rpm
>
> + INSTALL_FW_PATH=/root/rpmbuild/BUILDROOT/kernel-4.14.0_rc1+-22.x86_64/lib/firmware/4.14.0-rc1+
> + make INSTALL_FW_PATH=/root/rpmbuild/BUILDROOT/kernel-4.14.0_rc1+-22.x86_64/lib/firmware/4.14.0-rc1+
> firmware_install
> make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent
> make rule.
> make[2]: *** No rule to make target 'firmware_install'. Stop.
>
> I have to hack the script to compile through:
> diff --git a/scripts/package/mkspec b/scripts/package/mkspec
> index bb43f15..cb9c1b3 100755
> --- a/scripts/package/mkspec
> +++ b/scripts/package/mkspec
> @@ -92,7 +92,7 @@ echo 'mkdir -p $RPM_BUILD_ROOT'"/lib/firmware/$KERNELRELEASE"
>
> echo 'INSTALL_MOD_PATH=$RPM_BUILD_ROOT make %{?_smp_mflags}
> KBUILD_SRC= mod-fw= modules_install'
> echo 'INSTALL_FW_PATH=$RPM_BUILD_ROOT'"/lib/firmware/$KERNELRELEASE"
> -echo 'make INSTALL_FW_PATH=$INSTALL_FW_PATH' firmware_install
> +echo 'make INSTALL_FW_PATH=$INSTALL_FW_PATH'
> echo "%ifarch ia64"
>
> Not sure if this is a regression but several version ago it works well.
See the maling list for fixes for this already :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-09-20 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 3:20 Error when building the kernel on top of 4.14-rc1 for target firmware_install? Yu Chen
2017-09-20 5:37 ` Greg Kroah-Hartman [this message]
2017-09-20 5:49 ` Yu Chen
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=20170920053750.GA29160@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yu.chen.surf@gmail.com \
/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.