https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lisp/gcl-2.6.14 fails to compile. Discovered on: amd64 (internal ref: ci)
Created attachment 848955 [details] build.log build log and emerge --info
Created attachment 848957 [details] 1-config.log 1-config.log
Created attachment 848959 [details] 2-config.log 2-config.log
Error(s) that match a know pattern in addition to what has been reported in the summary: checking for inline semantics... ./configure: line 4568: nm: command not found checking for leading underscore in object symbols... ./configure: line 5323: nm: command not found ./configure: line 5260: cpp: command not found ./configure: line 5323: nm: command not found cp: cannot stat 'gmp4/gmp.h': No such file or directory configure: error: ABI=amd64 is not among the following valid choices: 64 x32 32
(In reply to Agostino Sarubbo from comment #4) > checking for inline semantics... ./configure: line 4568: nm: command not > found > checking for leading underscore in object symbols... ./configure: line 5323: > nm: command not found > ./configure: line 5260: cpp: command not found > ./configure: line 5323: nm: command not found Aren't binutils and gcc installed on this computer??
(In reply to Andrey Grozin from comment #5) > (In reply to Agostino Sarubbo from comment #4) > > checking for inline semantics... ./configure: line 4568: nm: command not > > found > > checking for leading underscore in object symbols... ./configure: line 5323: > > nm: command not found > > ./configure: line 5260: cpp: command not found > > ./configure: line 5323: nm: command not found > Aren't binutils and gcc installed on this computer?? Please look at the tracker bug for 'tc-directly': bug 243502. ago likely has gcc-config[-native-symlinks] and binutils-config[-native-symlinks].
What's raison d’être of gcc-config[-native-symlinks] and binutils-config[-native-symlinks]? To make perfectly valid packages fail? I'd think that the development tools should be configured to *maximize* the number of source packages taken from somewhere in the net which compile successfully. Not to *minimize* it.
(In reply to Andrey Grozin from comment #7) > What's raison d’être of gcc-config[-native-symlinks] and > binutils-config[-native-symlinks]? To make perfectly valid packages fail? > I'd think that the development tools should be configured to *maximize* the > number of source packages taken from somewhere in the net which compile > successfully. Not to *minimize* it. -native-symlink is a valid simulation to check if a package respect CC,CXX,LD and so on
ci has reproduced this issue with version 2.6.15_pre3 - Updating summary.