Github messages for voidlinux
 help / color / mirror / Atom feed
From: imbsky <imbsky@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: delta: update to 0.1.1
Date: Sun, 31 May 2020 01:07:24 +0200	[thread overview]
Message-ID: <20200530230724.OwxbVsPLU-81TRj_NPkRE4U7vH4jSwHhS5actJNFzqQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22317@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

New comment by imbsky on void-packages repository

https://github.com/void-linux/void-packages/pull/22317#issuecomment-636396311

Comment:
Probably yes.

```console
error: failed to run custom build command for `onig_sys v69.2.0`
Caused by:
  process didn't exit successfully: `/builddir/delta-0.1.1/target/release/build/onig_sys-10237aa0f829094d/build-script-build` (exit code: 101)
--- stdout
cargo:warning=couldn't execute `llvm-config --prefix` (error: No such file or directory (os error 2))
cargo:warning=set the LLVM_CONFIG_PATH environment variable to a valid `llvm-config` executable
--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'libclang.so\', \'libclang-*.so\', \'libclang.so.*\'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"', /host/cargo/registry/src/github.com-1ecc6299db9ec823/bindgen-0.50.1/src/lib.rs:1711:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

  parent reply	other threads:[~2020-05-30 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 14:26 [PR PATCH] " imbsky
2020-05-26 14:51 ` [PR PATCH] [Updated] " imbsky
2020-05-26 15:43 ` ericonr
2020-05-26 15:48 ` ericonr
2020-05-26 15:50 ` ericonr
2020-05-26 15:55 ` [PR PATCH] [Updated] " imbsky
2020-05-26 16:21 ` imbsky
2020-05-26 16:22 ` ericonr
2020-05-26 16:22 ` ericonr
2020-05-26 18:49 ` [PR PATCH] [Updated] " imbsky
2020-05-26 19:03 ` imbsky
2020-05-26 19:11 ` [PR PATCH] [Updated] " imbsky
2020-05-26 19:38 ` imbsky
2020-05-26 19:47 ` imbsky
2020-05-26 20:18 ` imbsky
2020-05-30 22:43 ` ericonr
2020-05-30 23:07 ` imbsky [this message]
2020-05-31  2:56 ` ericonr
2020-05-31 16:22 ` [PR PATCH] [Merged]: " abenson
2020-05-30 19:03 [PR PATCH] " abenson
2020-05-30 21:39 ` imbsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200530230724.OwxbVsPLU-81TRj_NPkRE4U7vH4jSwHhS5actJNFzqQ@z \
    --to=imbsky@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).