Skip to content


php CLI busted; recompile w/LD_RUN_PATH #3

ahutchings opened this Issue · 7 comments

4 participants


When executing PHP on the CLI I'm getting the following message:
/app/php/bin/php: error while loading shared libraries: cannot open shared object file: No such file or directory


Sorry, yes, you're correct. The buildpack needs a recompile with LD_RUN_PATH set to look in the correct place. It'll get included in the next build.


As a temporary workaround, you can do heroku config:add LD_LIBRARY_PATH=/app/php/ext --app your-app-name

@tmaher tmaher was assigned

@tmaher Could you include the build script/commands you used to build the current binary? I can't seem to get parity with getting the mysqlclient library to use v5.1.61


@winglian - currently it was a manual hodgepodge of manual steps based on Pedro's initial docs, and me spinning up a one-off AWS instance using a stock AMI. ddollar wrote a more automated build system called Vulcan - - that uses our runtime servers to do builds. I'm going to be migrating to using Vulcan, and I'm tracking it in Issue #6 on this repo. Concurrent with that, I'll update instructions so people can try non-Vulcan builds too as the wish.


Thanks, That's what I've been doing as well. Which AMI are you starting with? I've got memcached with SASL support and a few other goodies working but I need to rebase it before submitting a pull request. Thanks!


The commands and AMI I'm using so far I've tracked in, but for some reason, the mysqlclient lib is stuck with 5.1.41 rather than 5.1.61


For the current build, I used the Ubuntu 10.04 64-bit AMI from Canonical (us-west-2 AMI: ami-ec0b86dc), with some various packages installed manually via apt to more closely mirror the Heroku runtimes. Going forward with Vulcan, it'll be using the Heroku Cedar runtimes, which are derived from Ubuntu 10.04. To get the exact package list, spin up a cedar app and run heroku run 'dpkg-query -W' --app your-app-name. You should assume x86_64.

@dzuelke dzuelke closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.