This is an auto-filed bug because net-dialup/mwavem calls ar directly. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: If you think it doesn't make sense fix these type of issues, I'd like to point out that won't be possible use a different AR implementation (like llvm-ar) by setting the AR variable. So this issue has been reproduced by setting the AR variable to x86_64-pc-linux-gnu-ar and by removing the /usr/bin/ar binary.
Created attachment 641340 [details] build.log build log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c3868b2816dccb819eb62eb0570be4d0eb57e413 commit c3868b2816dccb819eb62eb0570be4d0eb57e413 Author: Jakov Smolic <jakov.smolic@sartura.hr> AuthorDate: 2020-11-26 10:32:45 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2020-11-26 10:32:45 +0000 net-dialup/mwavem: port to EAPI 7 Closes: https://github.com/gentoo/gentoo/pull/18402 Closes: https://bugs.gentoo.org/724974 Closes: https://bugs.gentoo.org/707684 Package-Manager: Portage-3.0.9, Repoman-3.0.1 Signed-off-by: Jakov Smolic <jakov.smolic@sartura.hr> Signed-off-by: David Seifert <soap@gentoo.org> net-dialup/mwavem/files/mwavem-2.0-ar.patch | 10 ++++++ .../mwavem/files/mwavem-2.0-fno-common.patch | 22 ++++++++++++ net-dialup/mwavem/mwavem-2.0-r2.ebuild | 40 ++++++++++++---------- 3 files changed, 54 insertions(+), 18 deletions(-)
