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]
Date:	Mon, 20 Dec 2010 18:41:32 -0500
From:	Arnaud Lacombe <lacombar@...il.com>
To:	"Carlos R. Mafra" <crmafra2@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: Build regression: unknown option "visible"

Hi,

On Mon, Dec 20, 2010 at 6:30 PM, Carlos R. Mafra <crmafra2@...il.com> wrote:
> On Mo 20.Dez'10 at 12:37:26 -0500, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Mon, Dec 20, 2010 at 12:22 PM, Carlos R. Mafra <crmafra2@...il.com> wrote:
>> > After pulling latest git from Linus (v2.6.37-rc6-132-g55ec86f)
>> > I can't compile it anymore:
>> >
>> > [mafra@...ar:linux-2.6]$ make -j2 O=/mnt/ext4/kernel-output/
>> >  GEN     /mnt/ext4/kernel-output/Makefile
>> > scripts/kconfig/conf --silentoldconfig Kconfig
>> > drivers/i2c/algos/Kconfig:6: unknown option "visible"
>> > drivers/media/common/tuners/Kconfig:48: unknown option "visible"
>> > drivers/media/video/Kconfig:115: unknown option "visible"
>> > drivers/media/dvb/frontends/Kconfig:16: unknown option "visible"
>> > make[3]: *** [silentoldconfig] Fehler 1
>> > make[2]: *** [silentoldconfig] Fehler 2
>> >
>> > This was introduced by 37e3273ee52f ("media/video: convert Kconfig
>> > to use the menu's `visible' keyword"), but I did a quick search
>> > and apparently I am the only one with a broken build.
>> >
>> > In any case, that's a regression for me and therefore I'm reporting it.
>> >
>> > I can test patches etc and provide more info if needed.
>> >
>> Did you build from a clean tree or a dirty one ?
>
> It was the same one which I always compile after pulling.
> So there is compiled stuff in the build dir /mnt/ext4/kernel-output
> (in an external hd).
>
>> I know these is issue with Kbuild where the parser will not get
>> updated to the new version if the target already exist but is older
>> than the current "shipped" one.
>
> Hm, not sure what this means. Should I do a 'make clean' to get it
> back working?
>
yes.

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

Powered by blists - more mailing lists