[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACqU3MUC-m7AgEPG2C-V2SVKEhHxdYE8tOSFJvqO9Vq+JJEchw@mail.gmail.com>
Date: Tue, 6 Sep 2011 11:32:00 -0400
From: Arnaud Lacombe <lacombar@...il.com>
To: Matthieu CASTET <matthieu.castet@...rot.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>
Subject: Re: randconfig broken on choice
Hi,
On Tue, Sep 6, 2011 at 11:13 AM, Matthieu CASTET
<matthieu.castet@...rot.com> wrote:
> Hi,
>
> Arnaud Lacombe a écrit :
>> Hi,
>>
>> On Tue, Sep 6, 2011 at 4:52 AM, Matthieu CASTET
>> <matthieu.castet@...rot.com> wrote:
>>> Hi,
>>>
>>> I am using v3.1-rc4 and make randconfig look broken for choice.
>>> The choice config is always the same or choice entry can have more than one entry.
>>>
>> Could you includes testcases showing that behavior, please ?
> $ make randconfig
>
> $ grep -e SLUB -e SLAB -e SLOB .config
> # CONFIG_SLAB is not set
> CONFIG_SLUB=y
> CONFIG_SLOB=y
> # CONFIG_FAILSLAB is not set
>
> We have 2 choice selected (SLUB and SLOB). You may run randconfig (more than one
> time to get this result).
>
ok, I reproduced it with:
while true; do
make randconfig
CONFIG_SLAB=; CONFIG_SLOB=; CONFIG_SLUB=
source .config
if [ "${CONFIG_SLAB}${CONFIG_SLOB}${CONFIG_SLUB}" != "y" ]; then
break
fi
sleep 1
done
I wonder what set the flags originally...
- Arnaud
> Matthieu
>
--
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