linux-kernel - Re: [PATCH] kbuild: Use symbolic link to the source tree for out-of-tree build

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53BD048F.4000800@suse.cz>
Date:	Wed, 09 Jul 2014 10:59:59 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Masahiro Yamada <yamada.m@...panasonic.com>
CC:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH] kbuild: Use symbolic link to the source tree for out-of-tree
 build

On 2014-07-09 08:27, Masahiro Yamada wrote:
> Since commit 9da0763bd, the variable 'srctree' is set as follows:
> 
> [1] Building in the source tree
>       => srctree is set to '.'
> [2] Building in a subdir right under the source tree
>       => srctree is set to '..'
> [3] Other cases
>       => srctree is set to the absolute path to the source tree
> 
> Pros are more readable compiler messages, WARN_ON() etc.
> for case [1] and [2]. (but not [3])
> 
> Cons are we have to do build-test for 3 cases when adding
> some changes to the build infrastructure.
> 
> We want to treat case [2] and [3] in the same way like prior to
> commit 9da0763bd, keeping the compact log messages.
> 
> The idea here is to create a symbolic link 'srctree' pointing
> to $(KBUILD_SRC) at the very early stage of the build process.

If the symlink points to an absolute path, then you can't move the
source and build tree around anymore.

Michal

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/