From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] Use relative path when creating include/asm/{mach,cpu}
Date: Tue, 18 Mar 2008 07:31:00 +0000 [thread overview]
Message-ID: <47DF6FB4.3090802@gmail.com> (raw)
In-Reply-To: <47DEC594.6010502@gmail.com>
Paul Mundt wrote:
> On Mon, Mar 17, 2008 at 08:25:08PM +0100, Franck Bui-Huu wrote:
>> From: Franck Bui-Huu <fbuihuu@gmail.com>
>>
>> Usually relative paths are preferred because they survive directory
>> moves, work across networked file systems/chrooted environments.
>>
> Usually, yes. But in this case, as Stuart noted, they are needed for
> out-of-tree builds.
>
Yes I've just checked and the patch won't work as is.
> It would be nice to get rid of the symlinks completely, and Sam had some
> ideas on how we could do that by doing a massive header reorganization,
> which is probably the way we'll go in the longer run.
Sure, the patch I sent is just a 'fix' for building a kernel tree across
NFS for example.
> For now we just have to live with the obfuscation. Patches that clean
> it up without breaking existing behaviour are welcome, though.
>
Well it should be pretty trivial to make this patch works both cases
although it can't be called a "clean up" patch.
Thanks,
Franck
next prev parent reply other threads:[~2008-03-18 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 19:25 [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Franck Bui-Huu
2008-03-17 19:51 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} Stuart MENEFY
2008-03-18 3:11 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Paul Mundt
2008-03-18 7:26 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} Franck Bui-Huu
2008-03-18 7:31 ` Franck Bui-Huu [this message]
2008-03-18 19:04 ` Franck Bui-Huu
2008-03-21 3:39 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Paul Mundt
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=47DF6FB4.3090802@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-sh@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