github.com/j8r/crystal-autobind
0.5.1 / published Nov 17, 2018 / repository
Automatic C binding generator for Crystal
Documentation could not be built
Build failed
The documentation build for this version ran and did not produce anything usable. That is usually a shard that does not compile against the Crystal version it declared.
What the builder reported
docs-build: this shard did not compile. The compiler reports that a command run by
docs-build: one of its macros failed.
docs-build:
docs-build: If that command reads from the network, that is why: documentation is
docs-build: compiled with no network access, because compiling a shard runs its
docs-build: macros and a build allowed to make requests is a build any published
docs-build: shard can use to reach our infrastructure. The command named below is
docs-build: the one to remove or to guard so that it tolerates failing.
docs-build: a command run by a macro failed during compilation
crystal docs said:
no-egress: verified in-process as uid 1000, ip and vsock sockets denied, io_uring denied, no_new_privs set
Crystal built without LibXML2 support, HTML sanitization will be skipped
Showing last frame. Use --error-trace for full trace.
In lib/clang/src/lib_clang.cr:6:19
6 | `[ -n "$LLVM_CONFIG" ] && command -v "$LLVM_CONFIG" || \
^
Error: error executing command: [ -n "$LLVM_CONFIG" ] && command -v "$LLVM_CONFIG" || command -v llvm-config-6.0 || command -v llvm-config60 || command -v llvm-config-5.0 || command -v llvm-config50 || command -v llvm-config-4.0 || command -v llvm-config40 || command -v llvm-config-3.9 || command -v llvm-config39 || command -v llvm-config
, got exit status 127