examples: can’t build from within subdirectory #740
Description
[nix-shell:~/kot/bazel/rules_haskell/examples]$ bazel build @io_tweag_rules_haskell_examples//vector/...
INFO: Invocation ID: 73d1dafd-1afc-4db2-ba27-93291bc342dc
INFO: Analysed 6 targets (3 packages loaded, 78 targets configured).
INFO: Found 6 targets...
INFO: Elapsed time: 26.572s, Critical Path: 25.82s
INFO: 32 processes: 32 linux-sandbox.
INFO: Build completed successfully, 59 total actions
[nix-shell:~/kot/bazel/rules_haskell/examples]$ bazel build //vector/...
INFO: Invocation ID: 2cdca67c-c1d8-4392-8aea-983e4b4f1265
INFO: Analysed 6 targets (0 packages loaded, 0 targets configured).
INFO: Found 6 targets...
ERROR: /home/philip/kot/bazel/rules_haskell/examples/vector/BUILD.bazel:18:1: error executing shell command: '/nix/store/1sa1jld0zjhdykmd8gp99bzkffba805v-bash/bin/bash -c
export PATH=${PATH:-} # otherwise GCC fails on Windows
# this is equivalent to 'readarray'. We do use 'readarray' in o...' failed (Exit 1) bash failed: error executing command /nix/store/1sa1jld0zjhdykmd8gp99bzkffba805v-bash/bin/bash -c ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
vector/Data/Vector/Fusion/Bundle.hs:110:2: error:
fatal error: vector.h: No such file or directory
^
|
110 |
| ^
compilation terminated.
`gcc' failed in phase `C pre-processor'. (Exit code: 1)
INFO: Elapsed time: 0.390s, Critical Path: 0.15s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
This might be some part of rules_haskell interacting weirdly with the /[-}>}?¹! workspace system.