Package: gcc-riscv64-unknown-elf Version: 8.3.0.2019.08+dfsg-1 Followup-For: Bug #979542
I've also observed this when trying to use gcc-riscv64 with the RIOT operating system, which (in contrast to Joel's initial report) sets a lot of potentially-needed flags and gets tested with other versions of the RISC-V GCC -- same result, the include_next fails. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.12.0-rc5 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gcc-riscv64-unknown-elf depends on: ii binutils-riscv64-unknown-elf 2.32.2020.04+dfsg-2 ii libc6 2.31-10 ii libgcc-s1 [libgcc1] 10.2.1-6 ii libgmp10 2:6.2.1+dfsg-1 ii libmpc3 1.2.0-1 ii libmpfr6 4.1.0-3 ii libstdc++6 10.2.1-6 ii zlib1g 1:1.2.11.dfsg-2 gcc-riscv64-unknown-elf recommends no packages. gcc-riscv64-unknown-elf suggests no packages. -- no debconf information
signature.asc
Description: PGP signature
