linux-kernel - Re: Symbol links to only needed and targeted source files

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 3 Jan 2007 23:35:10 +0100
From:	"Pelle Svensson" <pelle2004@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Symbol links to only needed and targeted source files

On 1/3/07, Sam Ravnborg <sam@...nborg.org> wrote:
> On Wed, Jan 03, 2007 at 10:14:43PM +0100, Pelle Svensson wrote:
> > Hi Sam,
> >
> > You misunderstand me I think, I already using a separate output directory.
> > What I like to do is a separate 'source tree' with only valid files
> > for my configuration. In that way, when I use grep for instance,
> > I would only hit valid files and not 50 other files which are
> > not in the current build configuration.
>
> I see.
> There is nothing in kbuild that will help you to achieve this.
> If you build the kernel and parse all .*.cmd files then
> you can build a complete list of files used and create your
> symlinked tree.
> But then you need a fully build kernel to do so.
>
> I see no easy way to get the info without building the kernel
> and if we do this only as a preprocessing step then we will
> most likely not integrate it in kbuild since the user base will
> be small. But if you hack up something lets take a look at it.
>
>         Sam
>

Hi Sam,

Ok, at least I know I'm not doing double work.

/Thanks
-
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/