CML2 1.9.1 installed over pristine 2.4.16. I double checked this time,
one brown paper bag a day is enough. Python 2.1, RH 7.2.
# rm .config config.out rules.out
# yes '' | make oldconfig
# grep BLUEZ .config config.out
.config:# CONFIG_BLUEZ is not set
.config:# CONFIG_BLUEZ_L2CAP is not set
.config:# CONFIG_BLUEZ_HCIUSB is not set
.config:# CONFIG_BLUEZ_HCIUART is not set
.config:# CONFIG_BLUEZ_HCIVHCI is not set
config.out:CONFIG_BLUEZ=n
config.out:CONFIG_BLUEZ_L2CAP=n
config.out:CONFIG_BLUEZ_HCIUSB=n
config.out:CONFIG_BLUEZ_HCIUART=n
config.out:CONFIG_BLUEZ_HCIVHCI=n
# make oldconfig
# grep BLUEZ .config config.out
.config:# CONFIG_BLUEZ is not set
config.out:CONFIG_BLUEZ=n
# make oldconfig
...
BLUEZ: Bluetooth subsystem support < >: (FROZEN)
BLUEZ_HCIUSB: HCI USB driver < > (NEW)?:
Why does the second make oldconfig get rid of BLUEZ_L2CAP and friends?
Why is the third oldconfig even asking for BLUEZ_HCIUSB? It goes:
net/rules.cml:
menu net # Networking options
...
BLUEZ? {bluetooth}
net/bluetooth/rules.cml:
menu bluetooth
BLUEZ_L2CAP? bluetooth_drivers
drivers/bluetooth/rules.cml:
menu bluetooth_drivers
BLUEZ_HCIUSB? BLUEZ_HCIUART? BLUEZ_HCIVHCI?
AFAICT when BLUEZ==n, none of the bluetooth menus or items should
appear, but they do. Adding
unless BLUEZ!=n suppress bluetooth_drivers
to net/bluetooth/rules.cml is a workaround but why is it needed?
BTW, symbols.cml has a typo:
bluetooth_drivers 'Blutooth drivers'
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
