https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-arch/unalz-0.65-r1 calls cc directly. Discovered on: amd64 (internal ref: guru_ci) NOTE: As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks] and set the CC variable to x86_64-pc-linux-gnu-gcc.
Created attachment 701250 [details] build.log build log and emerge --info
Possible context of error(s): make: gcc: No such file or directory
I can try to port this to meson if it's of any help, but with the following caveats: 1. I can't make promises about when, it could be tonight, it could be next year 2. I can't make promises about maintaining it in case there are upstream changes (unlikely since it's been unchanged for years afaict) I will attempt this if it's of any help, just let me know please
Changing the Assignee as per https://archives.gentoo.org/gentoo-dev/message/74ee632e9fe2f4c12890524fec132205
Does that mean I should attempt the port?
Changing TRACKER as requested by QA.
???
(In reply to Michele Santullo from comment #7) > ??? This is an automatically filed bug, and the previous two comments from Agostino have just been automated messages when mass changing the assignee/tracker for every GURU bug. As the note in the original comment notes: (In reply to Agostino Sarubbo from comment #0) > As per QA policy, toolchain tools must not be called directly because they > can cause issue in cross-compiling and because is not possible use a > different CC implementation (like clang). To reproduce, please use > sys-devel/gcc-config[-native-symlinks], > sys-devel/binutils-config[-native-symlinks] and set the CC variable to > x86_64-pc-linux-gnu-gcc. The error in the build log shows the toolchain (gcc in this case) being called directly from the Makefile. Because this version of the tinerbox does not symlink `/usr/bin/gcc` to the actual compiler executable you get an error. > make: gcc: No such file or directory (In reply to Michele Santullo from comment #3) > I will attempt this if it's of any help, just let me know please Porting to Meson might help but it's a real overkill for the issue here. Within the unalz-0.65-r1 Makefile the first two lines set the variables CPP & CC as g++ & gcc, respectively. These should not be set explicitly by the makefile and instead be set by the environment. You can achieve that by either removing those lines (I think) so they aren't set to begin with, or replace the `=` with `?=` so they are not set if those variables are already set in the environment like they are when emerginig. You could probably also pass CC=$(tc-get CC) or something like that to the emake command in src_compile
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=681e65013fae37e64f5b37d85179f98ad44bb2fe commit 681e65013fae37e64f5b37d85179f98ad44bb2fe Author: Joe Kappus <joe@wt.gd> AuthorDate: 2024-04-17 10:17:17 +0000 Commit: Joe Kappus <joe@wt.gd> CommitDate: 2024-04-17 10:25:37 +0000 app-arch/unalz: update EAPI 7 -> 8, fixups Major fixups, didn't revbump as nobody could build this for years. It needs a little more to work with clang, but with gcc it's fine. Closes: https://bugs.gentoo.org/784506 Closes: https://bugs.gentoo.org/900995 Signed-off-by: Joe Kappus <joe@wt.gd> app-arch/unalz/Manifest | 4 +-- .../files/unalz-0.65-respect-compiler-flags.patch | 36 ++++++++++++++++++++++ app-arch/unalz/unalz-0.65-r1.ebuild | 30 ++++++++++-------- 3 files changed, 56 insertions(+), 14 deletions(-)
