Am Montag, den 22.08.2011, 19:46 +0100 schrieb Lukas-David Gorris:
> Hey,
>
> I made this patch to add the htcleo (hd2) devices machine
> configuration and kernel recipe in meta-smartphone.
[...]
It seems that I was a bit too fast. There is a compile error in the
kernel added by this patch:
drivers/net/usb/asix.c:1226:6: warning: variable 'phyid' set but not
used [-Wunused-but-set-variable]
drivers/net/usb/asix.c:1225:6: warning: variable 'gpio0' set but not
used [-Wunused-but-set-variable]
CC [M] drivers/net/usb/cdc_ether.o
CC [M] drivers/net/usb/cdc_eem.o
CC [M] drivers/net/usb/dm9601.o
CC [M] drivers/net/usb/smsc95xx.o
CC [M] drivers/net/usb/gl620a.o
CC [M] drivers/net/usb/net1080.o
CC [M] drivers/net/usb/plusb.o
CC [M] drivers/net/usb/rndis_host.o
CC [M] drivers/net/usb/cdc_subset.o
CC [M] drivers/net/usb/zaurus.o
CC [M] drivers/net/usb/mcs7830.o
drivers/net/usb/mcs7830.c: In function 'mcs7830_set_autoneg':
drivers/net/usb/mcs7830.c:299:19: warning: the omitted middle operand
in ?: will always be 'true', suggest explicit middle operand
[-Wparentheses]
CC [M] drivers/net/usb/usbnet.o
CC [M] drivers/net/usb/int51x1.o
CC [M] drivers/net/wireless/bcm4329_204/dhd_linux.o
drivers/net/wireless/bcm4329_204/dhd_linux.c: In function
'dhd_rx_frame':
drivers/net/wireless/bcm4329_204/dhd_linux.c:997:24: error: variable
'save_pktbuf' set but not used [-Werror=unused-but-set-variable]
drivers/net/wireless/bcm4329_204/dhd_linux.c: In function
'dhd_os_wd_timer':
drivers/net/wireless/bcm4329_204/dhd_linux.c:2396:14: error: variable
'save_dhd_watchdog_ms' set but not used
[-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
This problem did not occur in my old org.oe.dev based setup and I used
the same htcleo metadata back then.
"cc1: all warnings being treated as errors". According to Martin, this
change is caused by gcc update to 4.6.
For intervention I suggest a workaround that will go back to the old
state where all warnings are treated as warnings and not as errors for
this particular kernel recipe. The correct solution - also suggested by
Martin - cleaning the code is currently not feasible imho as the kernel
is super messy ('android device').
How could we work around this?
All the best,
Lukas
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
