Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libplacebo-2.72.2 fails to build due to glslang / path issue #108723

Closed
jboyens opened this issue Jan 7, 2021 · 3 comments · Fixed by #108727
Closed

libplacebo-2.72.2 fails to build due to glslang / path issue #108723

jboyens opened this issue Jan 7, 2021 · 3 comments · Fixed by #108727
Labels
0.kind: bug Something is broken

Comments

@jboyens
Copy link
Contributor

jboyens commented Jan 7, 2021

Describe the bug
libplacebo-2.72.2 fails to build due to missing glslang header file

To Reproduce
Steps to reproduce the behavior:

  1. Check out rev f6f4e1f7be19dab2700385fe7b4f3d20a95a55bd
  2. Attempt to build libplacebo (dep. of mpv / mpv-with-scripts)
  3. Recieve the below error message
builder for '/nix/store/169s5i8v24bmi25dpg7wkd2v3yxdkdcn-libplacebo-2.72.2.drv' failed with exit code 1; last 10 log lines:
  build flags: -j12 -l12
  [23/44] Compiling C++ object src/libplacebo.so.72.p/glsl_glslang.cc.ols_gen.c.o
  FAILED: src/libplacebo.so.72.p/glsl_glslang.cc.o
  g++ -Isrc/libplacebo.so.72.p -Isrc -I../src -I../src/include -I../src/include/dummy -I../subprojects/xtalloc/include -I../subprojects/bstr/include -I/nix/store/zdw72aaz9zf2q4rqg3qdrha320mnddz5-lcms2-2.11-dev/include -I/nix/store/n3d8q3h7qdmx2zy2yxwn8zxjx6l9rsh0-vulkan-loader-1.2.162.0-dev/include -I/nix/store/azwvk8yg6n4pwjbhfgajfywrmj4vhx8f-epoxy-1.5.4-dev/include -I/usr/include/glslang -I/nix/store/50fq4bhc10fxsy5h47d908rr0yi1yyz5-libplacebo-2.72.2/include/glslang -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -std=c++11 -Wundef -Wshadow -Wparentheses -Wpointer-arith -fvisibility=hidden -fPIC -pthread -MD -MQ src/libplacebo.so.72.p/glsl_glslang.cc.o -MF src/libplacebo.so.72.p/glsl_glslang.cc.o.d -o src/libplacebo.so.72.p/glsl_glslang.cc.o -c ../src/glsl/glslang.cc
  ../src/glsl/glslang.cc:29:10: fatal error: SPIRV/GlslangToSpv.h: No such file or directory
     29 | #include <SPIRV/GlslangToSpv.h>
        |          ^~~~~~~~~~~~~~~~~~~~~~
  compilation terminated.
  [34/44] Compiling C object src/libplacebo.so.72.p/vulkan_context.c.o[K
  ninja: build stopped: subcommand failed.

Notify maintainers
@primeos @tadeokondrak

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.4, NixOS, 21.03.20210104.4a55ebe (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20201201_5a6ddb3`
 - nixpkgs: `/nix/store/j0mfic9x0i9pyhdixag6885wigky0dzx-source`

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute: 
# a list of nixos modules affected by the problem
module:
@jboyens jboyens added the 0.kind: bug Something is broken label Jan 7, 2021
@primeos
Copy link
Member

primeos commented Jan 7, 2021

Thanks for the report!
This is a regression from 31bd596. Seems like glslang broke something again... :o I didn't find any existing upstream issues/patches so far.

Edit: Not sure yet what changed. include/glslang/SPIRV/GlslangToSpv.h is still there. -I/usr/include/glslang seems like the problem, no idea where that comes from (maybe the pkg-config file is broken - but the diff looks fine).

@baloo
Copy link
Member

baloo commented Jan 7, 2021

Because glslang bumped from 8.13 to 11.1, so the include path changes from:

/nix/store/jg092gfgx0qw7j17wg8m6dd0qyknrvhd-glslang-8.13.3743/include/SPIRV

to:

/nix/store/cf1xbgkmqm19888pcvk8l1bmg1m18vlw-glslang-11.1.0/include/glslang/SPIRV

Note: glslang/SPIRV includes also works on 8.13:

/nix/store/jg092gfgx0qw7j17wg8m6dd0qyknrvhd-glslang-8.13.3743/include/glslang/SPIRV

@primeos primeos linked a pull request Jan 7, 2021 that will close this issue
10 tasks
primeos pushed a commit that referenced this issue Jan 7, 2021
@primeos
Copy link
Member

primeos commented Jan 7, 2021

@baloo thanks, I missed that change (only checked that the file didn't move in the source repo :o).

If someone is interested and has time: Feel free to submit a PR. It's getting late here and I cannot handle it before tomorrow. (I wrote this while the notification came :D)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants