armv5tel-softfloat-linux-gnueabi-gcc -MMD -O2 -pipe -march=armv5te -D'CONFIG_DEFAULT_PROGRAMMER=PROGRAMMER_INVALID' -D'CONFIG_INTERNAL=1' -D'CONFIG_SERPROG=1' -D'CONFIG_BITBANG_SPI=1' -D'CONFIG_DUMMY=1' -D'CONFIG_LINUX_SPI=1' -D'NEED_PCI=1' -D'HAVE_UTSNAME=1' -D'FLASHROM_VERSION="0.9.7-r1711"' -o bitbang_spi.o -c bitbang_spi.c bitbang_spi.c:67:11: error: 'SPI_CONTROLLER_BITBANG' undeclared here (not in a function) .type = SPI_CONTROLLER_BITBANG, ^ Reproducible: Always Steps to Reproduce: USE="bitbang_spi dummy internal linux_spi serprog tools -buspirate_spi -dediprog -drkaiser -ft2232_spi -gfxnvidia -nicintel -nicintel_spi -ogp_spi -pony_spi -satasii -static -usbblaster -wiki" emerge flashrom
Created attachment 403386 [details] /var/portage/logs/build/sys-apps/flashrom-0.9.7\:20150516-133346.log
0.9.8 with USE="linux_spi tools (-atahpt) -atavia -buspirate_spi -dediprog -drkaiser -dummy -ft2232_spi -gfxnvidia -internal -internal_dmi -it8212 -mstarddc_spi (-nic3com) -nicintel -nicintel_eeprom -nicintel_spi (-nicnatsemi) (-nicrealtek) -ogp_spi -pickit2_spi -pony_spi (-rayer_spi) (-satamv) -satasii -serprog -static -usbblaster_spi -wiki" builds fine.
CONFIG_BITBANG_SPI is actually not a real user-configurable parameter. One can actively set it as is done here but it does not really make sense and breaks the build if no bit-banging programmer is activated as well to enable the definition of SPI_CONTROLLER_BITBANG. I am planning to rename it in the future. I have no idea about gentoo, but it should probably not "export" this variable for use in the USE configuration.
(In reply to stefan.tauner from comment #3) > I have no idea about gentoo, but it should probably not "export" this > variable for use in the USE configuration. Yes, it shouldn't be a USE flag. I've been wanting to fix the bad things in the ebuild but I'm just too busy.
this was fixed when the 0.9.8 version bump was done