php CLI busted; recompile w/LD_RUN_PATH #3

Closed
ahutchings opened this Issue Feb 14, 2012 · 7 comments

Comments

Projects
None yet
4 participants
@ahutchings

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

@tmaher

This comment has been minimized.

Show comment
Hide comment
@tmaher

tmaher Apr 2, 2012

Contributor

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.

Contributor

tmaher commented Apr 2, 2012

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.

@tmaher

This comment has been minimized.

Show comment
Hide comment
@tmaher

tmaher Apr 2, 2012

Contributor

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

Contributor

tmaher commented Apr 2, 2012

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

@ghost ghost assigned tmaher Apr 2, 2012

@winglian

This comment has been minimized.

Show comment
Hide comment
@winglian

winglian Apr 2, 2012

@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 commented Apr 2, 2012

@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

@tmaher

This comment has been minimized.

Show comment
Hide comment
@tmaher

tmaher Apr 2, 2012

Contributor

@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 - https://github.com/heroku/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.

Contributor

tmaher commented Apr 2, 2012

@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 - https://github.com/heroku/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.

@winglian

This comment has been minimized.

Show comment
Hide comment
@winglian

winglian Apr 2, 2012

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!

winglian commented Apr 2, 2012

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!

@winglian

This comment has been minimized.

Show comment
Hide comment
@winglian

winglian Apr 2, 2012

The commands and AMI I'm using so far I've tracked in https://github.com/winglian/heroku-buildpack-php/blob/master/README.md, but for some reason, the mysqlclient lib is stuck with 5.1.41 rather than 5.1.61

winglian commented Apr 2, 2012

The commands and AMI I'm using so far I've tracked in https://github.com/winglian/heroku-buildpack-php/blob/master/README.md, but for some reason, the mysqlclient lib is stuck with 5.1.41 rather than 5.1.61

@tmaher

This comment has been minimized.

Show comment
Hide comment
@tmaher

tmaher Apr 2, 2012

Contributor

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.

Contributor

tmaher commented Apr 2, 2012

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 added a commit that referenced this issue Apr 11, 2014

Merge pull request #3 from pvh/patch-1
Updated usage instructions.

@dzuelke dzuelke closed this Apr 30, 2014

rikur pushed a commit to rikur/heroku-buildpack-php that referenced this issue Jul 6, 2016

rikur pushed a commit to rikur/heroku-buildpack-php that referenced this issue Jul 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment