-
-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
heroku fails to run due to invalid interpreter #15262
Comments
The patchelf issue looks like NixOS/patchelf#66. An alternative to creating a symlink is to invoke the interpreter directly, as in |
The heroku "binary" is really a ruby wrapper, so we need we dig into the ruby code to find the part where the go binary is being called and then prefix that with the correct interpreter. Looks a little bit messy to me... |
Actually, it looks more like the |
Sure, it certainly did work - but I think the change is that they are now depending on |
That makes sense @ocharles. So now 2 questions come to mind:
|
Any updates here? |
1 similar comment
Any updates here? |
I have a PR #18532 that should fix it, but until NixOS/patchelf#66 is fixed, we cannot patch the downloaded binary. If you want a temporary workaround, create a symlink in |
Closing this as things are now working using |
@peterhoeg the wrapper script does not seem to pass any command line arguments, so heroku is useless now. (might be worth a separate issue, but I'm in a hurry.) |
Submitted a fix: #22338 |
I have a proper fix without the ugly wrapper script. 5 min. |
@rasendubi, can you try out that PR? It also solves the psql issue. |
Issue description
The
heroku
package is broken immediately after installation as the package it downloads has an invalidinterpreter
set.Additionally, the
ld-linux-x86-64.so.2
symlink is not present in/run/current-system/sw/lib
(this may be a different issue)Steps to reproduce
First install
nix-env -i heroku
Then:
Notice the interpreter:
If I then try to set the interpreter using
patchelf
, I get an error about a missing section:And furthermore, the
ld-linux-x86-64.so.2
symlink is not present in/run/current-system/sw/lib
(this may be a different issue).The only way I can get heroku to run, is to manually make a symlink in /lib64 to the
ld-linux-x86-64.so.2
file in the nix store. Heroku then runs.Technical details
cc: @aflatter @mirdhyn
The text was updated successfully, but these errors were encountered: