Summary: | dev-libs/serd-0.30.14-r1:0 - ../.../meson.build: ERROR: Unknown compiler(s): [[clang]] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Professional Audio Applications Maintainers <proaudio> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | eschwartz93 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 870412 | ||
Attachments: |
emerge-info.txt
dev-libs:serd-0.30.14-r1:20220916-180929.log emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2022-09-16 19:12:12 UTC
Created attachment 805972 [details]
emerge-info.txt
Created attachment 805975 [details]
dev-libs:serd-0.30.14-r1:20220916-180929.log
Created attachment 805978 [details]
emerge-history.txt
Created attachment 805981 [details]
environment
Created attachment 805984 [details]
etc.portage.tar.bz2
Created attachment 805987 [details]
logs.tar.bz2
Created attachment 805990 [details]
temp.tar.bz2
in logs.tar.bz2 -> meson-logs/meson-log.txt ``` Detecting compiler via: clang --version compiler returned <Popen: returncode: 0 args: ['clang', '--version']> compiler stdout: compiler stderr: ../serd-0.30.14/meson.build:4:0: ERROR: Unknown compiler(s): [['clang']] ``` This clang command is successfully exiting, without emitting any content on stdout/stderr, even when asked to do so. From temp.tar.bz2, it seems clang is a wrapper script that redirects all output to a log file clang14.log / clang15.log, and then to /dev/null; these two log files are also in that tarball, and contain the output that Meson expected to see for the --version information. The wrapper script is really weird: ``` # Non-Autoconf configure scripts might try to parse stderr/stdout, so just run # it again... if [[ -f configure ]] && ! grep -q "#.*Generated by Autoconf" configure ; then clang-15 $@ else exit ${x[0]} fi ``` Only configure scripts? And what do those do -- just run every compilation twice?, so packages build half as fast? :o Anyway, Meson does assuredly parse stdout/stderr, so at least check for that too. yes, see the tracker bug for details and motivation, obviously this isn't a meson issue and it's the wrapper being too cheesy. I'll have a play in a bit (probably have one of them emit output and not the other). The duplicates are fine, I'll just en-masse mark them as such later. (Thinking about it, I'm not sure why i didn't end up just always execing again!) Ah, I see, even the wrapper itself is just a temporary thing. Didn't realize that. *** Bug 870532 has been marked as a duplicate of this bug. *** *** Bug 870511 has been marked as a duplicate of this bug. *** *** Bug 870508 has been marked as a duplicate of this bug. *** *** Bug 870496 has been marked as a duplicate of this bug. *** *** Bug 870505 has been marked as a duplicate of this bug. *** *** Bug 870469 has been marked as a duplicate of this bug. *** (In reply to Eli Schwartz from comment #11) > Ah, I see, even the wrapper itself is just a temporary thing. Didn't realize > that. no problem & sorry for the noise! Latest version of wrapper should be OK, just need toralf to pull it down. Fixed. *** Bug 870562 has been marked as a duplicate of this bug. *** |