Bug 695312 – dev-libs/opencl-clang-8.0.1 : /.../common_clang.cpp:54:10: fatal error: LLVMSPIRVLib/LLVMSPIRVLib.h: No such file or directory

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Toralf Förster 2019-09-21 13:46:45 UTC]

FAILED: CMakeFiles/opencl-clang.dir/common_clang.cpp.o 
/usr/bin/x86_64-pc-linux-gnu-g++ -DCOMMON_CLANG_EXPORTS -DLIBCOMMON_CLANG_NAME=\"libopencl-clang.so.8\" -DUSE_PREBUILT_LLVM -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -I/usr/lib/llvm/8/include -I. -I.  -DNDEBUG -O2 -pipe -march=native -fPIC     -std=gnu++11 -MD -MT CMakeFiles/opencl-clang.dir/common_clang.cpp.o -MF CMakeFiles/opencl-clang.dir/common_clang.cpp.o.d -o CMakeFiles/opencl-clang.dir/common_clang.cpp.o -c /var/tmp/portage/dev-libs/opencl-clang-8.0.1/work/opencl-clang-8.0.1/common_clang.cpp
/var/tmp/portage/dev-libs/opencl-clang-8.0.1/work/opencl-clang-8.0.1/common_clang.cpp:54:10: fatal error: LLVMSPIRVLib/LLVMSPIRVLib.h: No such file or directory
   54 | #include "LLVMSPIRVLib/LLVMSPIRVLib.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_no-multilib_hardened-20190920-071633

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-9.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems)
  [2]   ruby25 (with Rubygems) *

java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.13.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

repository timestamp:

==> /var/db/repos/gentoo/metadata/timestamp.chk <==
Sat, 21 Sep 2019 09:26:12 +0000

emerge -qpvO dev-libs/opencl-clang
[ebuild  N    ] dev-libs/opencl-clang-8.0.1

[Comment 1 Toralf Förster 2019-09-21 13:47:01 UTC]

Created attachment 590508 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2019-09-21 13:47:13 UTC]

Created attachment 590510 [details]
dev-libs:opencl-clang-8.0.1:20190921-121112.log

[Comment 3 Toralf Förster 2019-09-21 13:47:16 UTC]

Created attachment 590512 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2019-09-21 13:47:19 UTC]

Created attachment 590514 [details]
environment

[Comment 5 Toralf Förster 2019-09-21 13:47:21 UTC]

Created attachment 590516 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2019-09-21 13:47:24 UTC]

Created attachment 590518 [details]
logs.tbz2

[Comment 7 Toralf Förster 2019-09-21 13:47:27 UTC]

Created attachment 590520 [details]
temp.tbz2

[Comment 8 Toralf Förster 2019-10-07 18:12:29 UTC]

MAy I asked what the fix is? B/c the issue does still occur.

[Comment 9 Marek Szuba (RETIRED) 2019-10-07 21:55:49 UTC]

(In reply to Toralf Förster from comment #8)
> MAy I asked what the fix is? B/c the issue does still occur.

Could you elaborate? The ebuild in question is absent from the tree (I removed it about 6 hours before you posted your comment) so I am somewhat confused regarding how it can still occur.

[Comment 10 Toralf Förster 2019-10-08 21:04:19 UTC]

(In reply to Marek Szuba from comment #9)
> (In reply to Toralf Förster from comment #8)
> > MAy I asked what the fix is? B/c the issue does still occur.
> 
> Could you elaborate? The ebuild in question is absent from the tree (I
> removed it about 6 hours before you posted your comment) so I am somewhat
> confused regarding how it can still occur.

The log is from 20190921-121112.log - at that time the ebuild was still there. Few hours later I just "press" the button to report it - and within just a short time frame I do not check again whether an ebuild vanished or not.

[Comment 11 Marek Szuba (RETIRED) 2019-10-09 09:02:15 UTC]

Ah, okay. Guess we shall see if this shows up again for the current state of the tree, then.