[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CEC18FF.9030807@oracle.com>
Date: Tue, 23 Nov 2010 11:41:51 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Zimny Lech <napohybelskurwysynom2010@...il.com>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux kbuild list <linux-kbuild@...r.kernel.org>
Subject: Re: linux-next: Tree for November 23 (randconfig problem?)
On 11/23/10 11:04, Zimny Lech wrote:
> 2010/11/23 Randy Dunlap <randy.dunlap@...cle.com>:
>> On Tue, 23 Nov 2010 16:43:22 +0100 Zimny Lech wrote:
>>
>>> Ave
>>>
>>> 2010/11/23 Stephen Rothwell <sfr@...b.auug.org.au>:
>>>> Hi all,
>>>>
>>>> Changes since 20101122:
>>>>
>>>
>>>
>>> Random config generator has failed :)
>>
>> Hi,
>> What do you mean by this?
>
> This is what I get from "make" after "make randconfig".
>
>> I'm not seeing any randconfig generator problems.
>> Are you using any options or inputs to kconfig?
>
> No.
>
> I'm using script below to build kernel - nothing really unusual. Log
> and config for this failed build are attached to previous email
[script deleted]
OK, I see what you mean (I can reproduce it), but I don't see how it
happens. It looks like, from drivers/usb/gadget/Kconfig:
#
# USB Gadget Drivers
#
choice
tristate "USB Gadget Drivers"
depends on USB_GADGET && USB_GADGET_SELECTED
default USB_ETH
none of the choices inside this choice block was enabled by the randconfig.
Anybody in linux-kbuild land see how that can happen?
Zimny, one way that you can work around this is to run:
$ yes '' | make
or
$ yes '' | make oldconfig
after the 'make randconfig'. That sets the unknown kconfig symbol(s) to their
default values.
>>> USB Gadget Support (USB_GADGET) [Y/n/?] y
>>> Debugging messages (DEVELOPMENT) (USB_GADGET_DEBUG) [Y/n/?] y
>>> Debugging information files (DEVELOPMENT) (USB_GADGET_DEBUG_FILES) [N/y/?] n
>>> Debugging information files in debugfs (DEVELOPMENT)
>>> (USB_GADGET_DEBUG_FS) [Y/n/?] y
>>> Maximum VBUS Power usage (2-500 mA) (USB_GADGET_VBUS_DRAW) [2] 2
>>> USB Peripheral Controller
>>> > 1. Renesas R8A66597 USB Peripheral Controller (USB_GADGET_R8A66597)
>>> 2. Renesas M66592 USB Peripheral Controller (USB_GADGET_M66592)
>>> choice[1-2?]: 1
>>> USB Gadget Drivers
>>> 1. Gadget Zero (DEVELOPMENT) (USB_ZERO)
>>> 2. Audio Gadget (EXPERIMENTAL) (USB_AUDIO)
>>> > 3. Ethernet Gadget (with CDC Ethernet support) (USB_ETH)
>>> 4. Serial Gadget (with CDC ACM and CDC OBEX support) (USB_G_SERIAL)
>>> 5. Printer Gadget (USB_G_PRINTER)
>>> 6. CDC Composite Device (Ethernet and ACM) (USB_CDC_COMPOSITE)
>>> 7. HID Gadget (USB_G_HID)
>>> 8. EHCI Debug Device Gadget (USB_G_DBGP)
>>> choice[1-8?]: 3
>>> RNDIS support (USB_ETH_RNDIS) [Y/n/?] (NEW) aborted!
>>>
>>> Console input/output is redirected. Run 'make oldconfig' to update
>>> configuration.
>>>
>>> make[3]: *** [silentoldconfig] Error 1
>>> make[2]: *** [silentoldconfig] Error 2
>>> make[1]: *** No rule to make target `include/config/auto.conf', needed
>>> by `include/config/kernel.release'. Stop.
>>> make: *** [sub-make] Error 2
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_DEBUG=y
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_DEBUG_FS=y
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_R8A66597=y
CONFIG_USB_R8A66597=y
# CONFIG_USB_GADGET_M66592 is not set
CONFIG_USB_GADGET_DUALSPEED=y
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not set
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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