From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
srinivas.eeda@oracle.com, Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] kbuild: rpm-pkg: fix two build breaks when O= is used
Date: Mon, 5 Nov 2018 17:25:58 +0800 [thread overview]
Message-ID: <6d7af3dc-36a4-837d-42df-f37b2940dda9@oracle.com> (raw)
In-Reply-To: <CAK7LNAQUie1D3=0o36idvxR7uLtGRaV-MCs5L_cPcuXj28inEw@mail.gmail.com>
On 2018/11/5 15:55, Masahiro Yamada wrote:
> Hi Zhenzhong,
>
> On Fri, Nov 2, 2018 at 8:26 PM Zhenzhong Duan<zhenzhong.duan@oracle.com> wrote:
>> Running 'make O=/build/kernel binrpm-pkg' failed with below two errors.
>>
>> Makefile:600: include/config/auto.conf: No such file or directory
>>
>> + cp make -C /mnt/root/kernel O=/build/kernel image_name make -f
>> /mnt/root/kernel/Makefile ...
>> cp: invalid option -- 'C'
>> Try 'cp --help' for more information.
>>
>> Export KBUILD_OUTPUT when O= is used so that it could be used in locating
>> include/config/auto.conf
>>
>> Use $srctree to locate source dir when generating image name, no matter
>> if O= is used.
>>
>> Signed-off-by: Zhenzhong Duan<zhenzhong.duan@oracle.com>
>
> Sorry for the breakage, and thanks for your report.
>
> I'd like to fix the issue in a cleaner way.
>
> See this:
> https://patchwork.kernel.org/patch/10667539/
Never mind, appreciate you fixed it in a smart way:)
Thanks
Zhenzhong
prev parent reply other threads:[~2018-11-05 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 11:25 [PATCH] kbuild: rpm-pkg: fix two build breaks when O= is used Zhenzhong Duan
2018-11-05 7:55 ` Masahiro Yamada
2018-11-05 9:25 ` Zhenzhong Duan [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=6d7af3dc-36a4-837d-42df-f37b2940dda9@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=srinivas.eeda@oracle.com \
--cc=yamada.masahiro@socionext.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 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).