Bug#903822: Package(s) broken by CLANG_RESOURCE_DIR change

2018-07-16 Thread Andreas Beckmann
Package: release.debian.org
Followup-For: Bug #903822

While this gets investigated at the llvm and package sides, please
schedule these binNMUs:

nmu pocl_1.1-5 . ANY . -m "Rebuild against llvm-toolchain-6.0 6.0.1"
nmu qtcreator_4.6.2-1 . ANY . -m "Rebuild against llvm-toolchain-6.0 6.0.1"


# libpocl2
strings /usr/lib/x86_64-linux-gnu/libpocl.so.2.1.0 | grep 
/usr/lib/llvm-6.0/lib/clang
/usr/lib/llvm-6.0/lib/clang/6.0.0/include/opencl-c.h

# mesa-opencl-icd
strings /usr/lib/x86_64-linux-gnu/libMesaOpenCL.so.1.0.0 | grep 
/usr/lib/llvm-6.0/lib/clang
/usr/lib/llvm-6.0/lib/clang/6.0.1

# qtcreator
strings /usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangCodeModel.so | grep 
/usr/lib/llvm-6.0/lib/clang
/usr/lib/llvm-6.0/lib/clang/6.0.0/include

I couldn't find evidence for irony-mode.


Andreas



Bug#903822: Package(s) broken by CLANG_RESOURCE_DIR change

2018-07-15 Thread Graham Inggs
Control: clone -1 -2
Control: reassign -2 src:llvm-toolchain-6.0 1:6.0.1-1
Control: retitle -2 resource directory changes with minor upstream release
Control: severity -2 important

Cloning and re-assigning so we can fix this for future releases.



Bug#903822: Package(s) broken by CLANG_RESOURCE_DIR change

2018-07-15 Thread Rebecca N. Palmer

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
(or should this be 'nmu'?)

The Clang resource directory (clang --print-resource-dir) changes every 
upstream *bugfix* release (e.g. /usr/lib/llvm-6.0/lib/clang/6.0.1/ ), 
but clang's reverse dependencies are only rebuilt every *feature* release.


At least pocl, and possibly also mesa-opencl-icd, qtcreator and 
irony-mode, store this directory name in CLANG_RESOURCE_DIR at build 
time then expect it to be the same at run time.


Hence, pocl is mostly unusable (clBuildProgram fails with
error: :2:10: 
'/usr/lib/llvm-6.0/lib/clang/6.0.0/include/opencl-c.h' file not found

); I haven't tested the others.

BinNMUs will probably fix the immediate problem, but it would recur on 
future bugfix releases.