Skip to content
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

Missing $LD_LIBRARY_PATH entry? #27

Open
artemave opened this issue Nov 28, 2017 · 1 comment · May be fixed by #38
Open

Missing $LD_LIBRARY_PATH entry? #27

artemave opened this issue Nov 28, 2017 · 1 comment · May be fixed by #38

Comments

@artemave
Copy link

My Aptfile contains only libaio1. The package is installed without problems, but when the app at runtime is trying to refer to it, the error is throws that libaio.so.1 can't be found.

I think that is because $LD_LIBRARY_PATH is missing its location:

flynn@9b481505-8ca2-44fc-87e2-a8f9e8fba8e3:~$ echo $LD_LIBRARY_PATH
OTHER_ENTRIES:/app/.apt/usr/lib/x86_64-linux-gnu:/app/.apt/usr/lib/i386-linux-gnu:/app/.apt/usr/lib:

But that file ends up in

flynn@9b481505-8ca2-44fc-87e2-a8f9e8fba8e3:~$ ls .apt/lib/x86_64-linux-gnu/
libaio.so.1  libaio.so.1.0.1

As you can see there is no /usr bit in there.

I have another buildpack of my own that follows after the apt one. I basically hacked that missing value in and that's how I managed to resolve the app's issue (https://github.com/featurist/oracle-client-buildpack/blob/master/profile/oracle-driver-buildpack-runtime-env.sh#L1):

artemave added a commit to featurist/oracle-client-buildpack that referenced this issue Jan 31, 2018
This time so libaio can be used at slug build time in addition to slug
run time.

This should be done by heroku-buildpack-apt, but it is not. heroku/heroku-buildpack-apt#27
@tribela tribela linked a pull request Aug 30, 2018 that will close this issue
@dzuelke
Copy link
Contributor

dzuelke commented Jun 14, 2022

Keeping this open for reference, but just to note: Ubuntu 20 and later have this particular package install to /usr/lib/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants