-
Notifications
You must be signed in to change notification settings - Fork 38
Release binary fails mysteriously. #239
Comments
@RAOF Hello fellow Nix user! I've just tried downloading https://github.com/vitiral/artifact/releases/download/2.0.0/artifact-2.0.0-x86_64-unknown-linux-gnu.tar.gz (from https://github.com/vitiral/artifact/releases) and it just works when dropped into Can you try |
Your original download link doesn't work anymore (expired), so it's different from what I've downloaded. |
Oh. Wait. You're not a NixOS user. It's the release binary that was built using NixOS! :D It just so happens that you have nix installed locally and |
It looks to me that What you get when doing Here:
it's just |
Aha! Passing an actual argument results in activity! I do not, in fact, have nix installed locally; It's not clear to me why I'm somewhat surprised this build works at all on non-nix systems, but I cannot be the first to have tried‽ |
You could try using patchelf to fix that path: https://nixos.org/patchelf.html |
Hey, sorry I've been AWOL. I think I should be able to address this this week. |
This should be fixed in release 2.0.1. Let me know any more issues! |
@vitiral You're back! Great. |
thanks! Still going to be on hiatus for a bit more, but starting to get back into things slowly. |
I've downloaded the release tarball from here, extracted it into
~/.local/bin
(which is in$PATH
) and then tried to run it on an Ubuntu 18.10 (Cosmic Cuttlefish) development system.It fails in an extremely odd way.
Huh.
Hm, maybe the oddly stored location for
ld-linux
is confusing it?Huh! Well, that at least loads. I wonder what the backtrace is?
Heh. Not very enlightening!
Other rust projects (notably, my own,
cargo
, andripgrep
) build and work fine on this system; I wonder what's odd with theart
binary?The text was updated successfully, but these errors were encountered: