This is an auto-filed bug because net-print/mtink calls cc 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 CC implementation (like clang) by setting the CC variable. So this issue has been reproduced by setting the CC variable to x86_64-pc-linux-gnu-gcc and by removing the /usr/bin/cc - /usr/bin/gcc binaries.
Created attachment 641546 [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=eab7bcd2b21a9fcdbeffa663549547007740e523 commit eab7bcd2b21a9fcdbeffa663549547007740e523 Author: Jakov Smolic <jakov.smolic@sartura.hr> AuthorDate: 2021-02-14 10:32:57 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2021-02-14 10:32:57 +0000 net-print/mtink: Fix build issues * Fix build with gcc-10 * Fix detection of lesstif library * Do not call CC directly * Fix broken README symlink Closes: https://bugs.gentoo.org/708040 Closes: https://bugs.gentoo.org/679324 Closes: https://bugs.gentoo.org/727952 Closes: https://bugs.gentoo.org/725196 Closes: https://bugs.gentoo.org/741062 Signed-off-by: Jakov Smolic <jakov.smolic@sartura.hr> Signed-off-by: David Seifert <soap@gentoo.org> net-print/mtink/files/mtink-1.0.16-flags.patch | 5 +-- .../mtink/files/mtink-1.0.16-fno-common.patch | 20 +++++++++ net-print/mtink/files/mtink-1.0.16-motif.patch | 49 ++++++++++++++++++++++ net-print/mtink/files/mtink-1.0.16-overflow.patch | 4 +- net-print/mtink/metadata.xml | 8 ++-- net-print/mtink/mtink-1.0.16-r2.ebuild | 35 ++++++++++------ 6 files changed, 100 insertions(+), 21 deletions(-)
