CC [M] /var/tmp/portage/net-misc/ena-driver-2.0.2/work/amzn-drivers-ena_linux_2.0.2/kernel/linux/ena/../common/ena_com//ena_com.o /var/tmp/portage/net-misc/ena-driver-2.0.2/work/amzn-drivers-ena_linux_2.0.2/kernel/linux/ena/../common/ena_com//ena_com.c: In function ‘ena_com_admin_init_sq’: /var/tmp/portage/net-misc/ena-driver-2.0.2/work/amzn-drivers-ena_linux_2.0.2/kernel/linux/ena/../common/ena_com//ena_com.c:114:16: error: implicit declaration of function ‘dma_zalloc_coherent’; did you mean ‘dma_alloc_coherent’? [-Werror=implicit-function-declaration] sq->entries = dma_zalloc_coherent(queue->q_dmadev, size, &sq->dma_addr, ^~~~~~~~~~~~~~~~~~~ dma_alloc_coherent ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-systemd_abi32+64_20190306-071626 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) Available Rust versions: [1] rust-1.32.0 * emerge -qpvO net-misc/ena-driver [ebuild N ] net-misc/ena-driver-2.0.2
Created attachment 568188 [details] emerge-info.txt
Created attachment 568190 [details] emerge-history.txt
Created attachment 568192 [details] environment
Created attachment 568194 [details] etc.portage.tbz2
Created attachment 568196 [details] net-misc:ena-driver-2.0.2:20190308-072727.log
This looks like wrong kernel options. I just bumped 2.2.3 which now tests config requirements
