linux-kernel - Re: [PATCH] Clarify CONFIG_DEBUG

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: <20140205054613.GA30094@gmail.com>
Date:	Wed, 5 Feb 2014 06:46:13 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	David Rientjes <rientjes@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Borislav Petkov <bp@...en8.de>,
	LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
	Richard Weinberger <richard@....at>,
	Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Tue, Feb 4, 2014 at 1:08 AM, Ingo Molnar <mingo@...nel.org> wrote:
> >
> >  config SAVE_TIME_AND_DISK_SPACE
> >         bool "Faster and leaner build object files: compile without debug info"
> >         default y
> 
> Thinking about it, we already have this. It's called "CONFIG_COMPILE_TEST".
> 
> It very much gets set by all{yes,mod}config, and it also says "we're
> interested in testing the compile, not so much running the result".
> 
> So let's just make the DEBUG_INFO depend on !COMPILE_TEST.
> 
> Trivial oneliner patch (independent of the discussion about improving
> the documentation), so I'll just apply it.
> 
> I can't imagine that this would be controversial:
> 
>    config DEBUG_INFO
>           bool "Compile the kernel with debug info"
>   -       depends on DEBUG_KERNEL
>   +       depends on DEBUG_KERNEL && !COMPILE_TEST
>           help
> 
> Hm?

Fully agreed.

Thanks,

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