linux-kernel - Re: [BUILD_FAILURE] 2.6.25-rc2-mm1

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:	Fri, 22 Feb 2008 10:29:38 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Nish Aravamudan <nish.aravamudan@...il.com>,
	Len Brown <lenb@...nel.org>,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: [BUILD_FAILURE] 2.6.25-rc2-mm1 - Build Failure at acpi_os

Sam Ravnborg wrote:
>> Is there a way to generate (in Kconfig language) the boolean
>> CONFIG_ACPI_CUSTOM_DSDT based on whether CONFIG_ACPI_CUSTOM_DSDT_FILE
>> == "" or != "" ?  I tried to muck around with that last night but
>> couldn't get it to work.  I.e., just present the ACPI_CUSTOM_DSDT_FILE
>> config symbol to the user and then generate the ACPI_CUSTOM_DSDT bool
>> based on the string value.
> 
> Something following this example?
> 
> config STRING
>         string
>         prompt "What string"
>         default ""
> 
> config STRING_IS_NOT_EMPTY
>         bool
>         default STRING != ""
> 
> 
> But that seems too easy - were you trying to do something
> more complex than this?

Yes, that's almost what I had.  I used def_bool n on the second config symbol,
but the bool value never changed when I changed the string value.
I'll be glad to look at it again though.

-- 
~Randy
--
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/