../flashrom-v1.2/ft2232_spi.c:27:10: fatal error: ftdi.h: No such file or directory 27 | #include <ftdi.h> | ^~~~~~~~ compilation terminated. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-20210123-232713 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.1 Python 3.8.7 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) * Available Rust versions: [1] rust-1.48.0 * The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon Jan 25 22:36:54 UTC 2021 emerge -qpvO sys-apps/flashrom [ebuild N ] sys-apps/flashrom-1.2-r3 USE="atavia buspirate-spi ch341a-spi dediprog developerbox-spi digilent-spi drkaiser dummy ft2232-spi gfxnvidia internal internal-dmi it8212 linux-mtd linux-spi nic3com nicintel nicintel-eeprom nicintel-spi nicrealtek ogp-spi pickit2-spi pony-spi rayer-spi satamv satasii serprog stlinkv3-spi usbblaster-spi -atahpt -atapromise -jlink-spi -mstarddc-spi -nicnatsemi -tools"
Created attachment 684735 [details] emerge-info.txt
Created attachment 684738 [details] emerge-history.txt
Created attachment 684741 [details] environment
Created attachment 684744 [details] etc.portage.tar.bz2
Created attachment 684747 [details] sys-apps:flashrom-1.2-r3:20210125-232135.log
Created attachment 684750 [details] temp.tar.bz2
The problem is that if dev-embedded/libftdi-1.5 is emerged with USE=cxx, the directory /usr/include/libftdipp1 ends up listed as includedir in both libftdipp1.pc and libftdi1.pc - even though the latter should point to /usr/include/libftdi1.
*** This bug has been marked as a duplicate of bug 766818 ***
