Problem with LD_LIBRARY_PATH & libreadline.so about ruby-buildpack

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/95976388.

[jtarchie]

After thorough investigation, we've determined that this not a readline problem.
It turns out that Jekyll was following a non-existent libreadline symlink when generating the static files. This is because the buildpack puts a symlink in place for the lucid64, which is not needed on cflinuxfs2.

When @nicwilliams disabled auto-generation, this caused the dead symlink to be followed, resulting in the above error.

libreadline works fine on CloudFoundry. We're not concerned about the dead symlink as it'll be going away with the death of lucid64. However, it's worth it to note that other issues would have followed had the libreadline symlink existed. For example, Jekyll would have attempted to copy in the rubies to the generated content.

When Jekyll is run on CF, care should be taken to ensure that the source directory is not the root directory. This is because CF will add files to /app, which then get traversed by Jekyll.

Closing. We'll remove libreadline symlink when lucid64 support is officially dropped from the buildpacks.