From: Julien Grall <julien.grall@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <mmarek@suse.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Fail to build Linux with O= in master
Date: Mon, 2 Oct 2017 12:20:54 +0100 [thread overview]
Message-ID: <f6634898-357b-0c9b-ac22-8e0ca225b290@arm.com> (raw)
In-Reply-To: <CAK7LNAQh=RDUCsxMfX0QY6w4NyeMdUdgc0GbXDP=SEWDzqKXWQ@mail.gmail.com>
Hello,
On 30/09/17 01:37, Masahiro Yamada wrote:
> 2017-09-30 8:59 GMT+09:00 Julien Grall <julien.grall@arm.com>:
>> Hello,
>>
>> I have tried to build the latest master and got the following error:
>>
>> 42sh> make O=~/works/linux-build/aarch64-4k -C ~/works/linux
>> make: Entering directory '/home/julgra01/works/linux'
>> Makefile:135: *** failed to create output directory "~/works/linux-build/aarch64-4k". Stop.
>> make: Leaving directory '/home/julgra01/works/linux'
>>
>> The bisector found the commit 8e9b466 "kbuild: use $(abspath ...)
>> instead of $(shell cd ... && /bin/pwd)".
>>
>> Looking at the code, it seems that it is because the code is
>> now using $(realpath ...). Indeed when I replace ~ by $HOME
>> the kernel is now built.
>>
>> I am not a Makefile expert, so I would appreciate if anyone
>> could suggest a patch for this.
>>
>
> Thanks for the report.
>
> Which shell are you using?
I am using dash.
>
> I use bash and I have no problem.
> If I try dash, indeed, it fails.
>
> I will take a look.
Thank you!
Cheers,
--
Julien Grall
prev parent reply other threads:[~2017-10-02 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 23:59 Julien Grall
2017-09-30 0:37 ` Masahiro Yamada
2017-10-02 11:20 ` Julien Grall [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=f6634898-357b-0c9b-ac22-8e0ca225b290@arm.com \
--to=julien.grall@arm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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
all inboxes | Powered by JetHome®