FAQ
Hi...

During my CF deployment attempt I see the CF vm downloading and compiling
packages from the blobstore (using dav I have the blobstore on my bosh vm).
  When it gets to ruby it fails during the make step with the following
error:

gcc -I. -I../../.ext/include/x86_64-linux -I../.././include
-I../.././ext/openssl -DRUBY_EXTCONF_H=\"extconf.h\"
-I/var/vcap/packages/libyaml/include -fPIC -O3 -ggdb -Wextra
-Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings
-Wno-missing-field-initializers -Wno-long-long -o ossl_ssl.o -c ossl_ssl.c
ossl_ssl.c:110:1: error: 'SSLv2_method' undeclared here (not in a function)
ossl_ssl.c:111:1: error: 'SSLv2_server_method' undeclared here (not in a
function)
ossl_ssl.c:112:1: error: 'SSLv2_client_method' undeclared here (not in a
function)
make[1]: *** [ossl_ssl.o] Error 1
make[1]: Leaving directory
`/var/vcap/data/compile/ruby/ruby-1.9.2-p180/ext/openssl'
make: *** [mkmain.sh] Error 1

Searching around it seems like most solutions to this are to use RVM. I
built this stemcell myself so I'm wondering if I missed an important step.
  Recently when I've installed ruby without rvm on Lucid for other projects
I do this:

apt-get install libssl-dev
./configure --with-openssl=/usr/lib/x86_64-linux-gnu

I don't see the "with-openssl" param being used in the bosh compile step.
  Did you guys ever see this problem and get around it when building the
public stemcells?

Thanks
Ethan

Search Discussions

  • Ferran Rodenas at Jul 23, 2013 at 11:18 pm
    What version of Ubuntu are you using for the stemcell? Seems similar to
    this issue:
    https://groups.google.com/a/cloudfoundry.org/d/msg/vcap-dev/cyx68x8eKmc/NoFfB-fu8AwJ

    - Ferdy


    2013/7/23 <ekmerril@gmail.com>
    Hi...

    During my CF deployment attempt I see the CF vm downloading and compiling
    packages from the blobstore (using dav I have the blobstore on my bosh vm).
    When it gets to ruby it fails during the make step with the following
    error:

    gcc -I. -I../../.ext/include/x86_64-linux -I../.././include
    -I../.././ext/openssl -DRUBY_EXTCONF_H=\"extconf.h\"
    -I/var/vcap/packages/libyaml/include -fPIC -O3 -ggdb -Wextra
    -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings
    -Wno-missing-field-initializers -Wno-long-long -o ossl_ssl.o -c ossl_ssl.c
    ossl_ssl.c:110:1: error: 'SSLv2_method' undeclared here (not in a function)
    ossl_ssl.c:111:1: error: 'SSLv2_server_method' undeclared here (not in a
    function)
    ossl_ssl.c:112:1: error: 'SSLv2_client_method' undeclared here (not in a
    function)
    make[1]: *** [ossl_ssl.o] Error 1
    make[1]: Leaving directory
    `/var/vcap/data/compile/ruby/ruby-1.9.2-p180/ext/openssl'
    make: *** [mkmain.sh] Error 1

    Searching around it seems like most solutions to this are to use RVM. I
    built this stemcell myself so I'm wondering if I missed an important step.
    Recently when I've installed ruby without rvm on Lucid for other projects
    I do this:

    apt-get install libssl-dev
    ./configure --with-openssl=/usr/lib/x86_64-linux-gnu

    I don't see the "with-openssl" param being used in the bosh compile step.
    Did you guys ever see this problem and get around it when building the
    public stemcells?

    Thanks
    Ethan
  • Matthew Sykes at Jul 23, 2013 at 11:22 pm
    I hit that problem when attempting to build cf_release on precise instead
    of lucid. If you want, you can patch the package with the diff at
    https://gist.github.com/13k/1039377#file-ruby-1-9-2-nossl2-diff to get
    beyond it.

    On Tue, Jul 23, 2013 at 4:45 PM, wrote:

    Hi...

    During my CF deployment attempt I see the CF vm downloading and compiling
    packages from the blobstore (using dav I have the blobstore on my bosh vm).
    When it gets to ruby it fails during the make step with the following
    error:

    gcc -I. -I../../.ext/include/x86_64-linux -I../.././include
    -I../.././ext/openssl -DRUBY_EXTCONF_H=\"extconf.h\"
    -I/var/vcap/packages/libyaml/include -fPIC -O3 -ggdb -Wextra
    -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings
    -Wno-missing-field-initializers -Wno-long-long -o ossl_ssl.o -c ossl_ssl.c
    ossl_ssl.c:110:1: error: 'SSLv2_method' undeclared here (not in a function)
    ossl_ssl.c:111:1: error: 'SSLv2_server_method' undeclared here (not in a
    function)
    ossl_ssl.c:112:1: error: 'SSLv2_client_method' undeclared here (not in a
    function)
    make[1]: *** [ossl_ssl.o] Error 1
    make[1]: Leaving directory
    `/var/vcap/data/compile/ruby/ruby-1.9.2-p180/ext/openssl'
    make: *** [mkmain.sh] Error 1

    Searching around it seems like most solutions to this are to use RVM. I
    built this stemcell myself so I'm wondering if I missed an important step.
    Recently when I've installed ruby without rvm on Lucid for other projects
    I do this:

    apt-get install libssl-dev
    ./configure --with-openssl=/usr/lib/x86_64-linux-gnu

    I don't see the "with-openssl" param being used in the bosh compile step.
    Did you guys ever see this problem and get around it when building the
    public stemcells?

    Thanks
    Ethan


    --
    Matthew Sykes
    matthew.sykes@gmail.com
  • Ferran Rodenas at Jul 23, 2013 at 11:28 pm
    Another approach is what we do when we install ruby on the bosh stemcell
    (not the same ruby installed for CF):
    https://github.com/cloudfoundry/bosh/blob/master/stemcell_builder/stages/bosh_ruby/apply.sh#L22

    - Ferdy


    2013/7/24 Matthew Sykes <matthew.sykes@gmail.com>
    I hit that problem when attempting to build cf_release on precise instead
    of lucid. If you want, you can patch the package with the diff at
    https://gist.github.com/13k/1039377#file-ruby-1-9-2-nossl2-diff to get
    beyond it.

    On Tue, Jul 23, 2013 at 4:45 PM, wrote:

    Hi...

    During my CF deployment attempt I see the CF vm downloading and compiling
    packages from the blobstore (using dav I have the blobstore on my bosh vm).
    When it gets to ruby it fails during the make step with the following
    error:

    gcc -I. -I../../.ext/include/x86_64-linux -I../.././include
    -I../.././ext/openssl -DRUBY_EXTCONF_H=\"extconf.h\"
    -I/var/vcap/packages/libyaml/include -fPIC -O3 -ggdb -Wextra
    -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -Wwrite-strings
    -Wno-missing-field-initializers -Wno-long-long -o ossl_ssl.o -c ossl_ssl.c
    ossl_ssl.c:110:1: error: 'SSLv2_method' undeclared here (not in a
    function)
    ossl_ssl.c:111:1: error: 'SSLv2_server_method' undeclared here (not in a
    function)
    ossl_ssl.c:112:1: error: 'SSLv2_client_method' undeclared here (not in a
    function)
    make[1]: *** [ossl_ssl.o] Error 1
    make[1]: Leaving directory
    `/var/vcap/data/compile/ruby/ruby-1.9.2-p180/ext/openssl'
    make: *** [mkmain.sh] Error 1

    Searching around it seems like most solutions to this are to use RVM. I
    built this stemcell myself so I'm wondering if I missed an important step.
    Recently when I've installed ruby without rvm on Lucid for other projects
    I do this:

    apt-get install libssl-dev
    ./configure --with-openssl=/usr/lib/x86_64-linux-gnu

    I don't see the "with-openssl" param being used in the bosh compile step.
    Did you guys ever see this problem and get around it when building the
    public stemcells?

    Thanks
    Ethan


    --
    Matthew Sykes
    matthew.sykes@gmail.com
  • Ekmerril at Jul 24, 2013 at 1:22 am
    Worked! Thanks for the quick response guys.

    Should this be part of the base cf-release repo for the ruby package? I
    would assume anybody starting from a base Ubuntu OS when building a
    stemcell would hit this problem unless there's a best practice for making
    the stemcell that would not require this update to the cf-release package.

    Ethan
  • Ferran Rodenas at Jul 24, 2013 at 9:16 pm
    CF-Release is only supported on Ubuntu 10.04 right now, so no need to apply
    the patch.

    - Ferdy


    2013/7/24 <ekmerril@gmail.com>
    Worked! Thanks for the quick response guys.

    Should this be part of the base cf-release repo for the ruby package? I
    would assume anybody starting from a base Ubuntu OS when building a
    stemcell would hit this problem unless there's a best practice for making
    the stemcell that would not require this update to the cf-release package.

    Ethan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-dev @
postedJul 23, '13 at 8:45p
activeJul 24, '13 at 9:16p
posts6
users3

People

Translate

site design / logo © 2021 Grokbase