Hi,
Thank you Alexander for the workaround. I updated the installer to use
ruby-1.9.3-p484 so those steps are no longer necessary.

Cheers,
Pawel


On 6 December 2013 20:41, Alexandre Beauclair <[email protected]>wrote:

> On Wednesday, December 4, 2013 8:50:01 AM UTC-5, Matthew Bowman wrote:
> > On Tuesday, December 3, 2013 4:22:27 PM UTC-5, [email protected]:
> >
> > > On Monday, December 2, 2013 5:11:47 AM UTC+1, George Slavov wrote:
> >
> > > > I had a look at this project a few weeks ago and then decided to
> wait for v3.0 of the community installer.
> >
> > > >
> >
> > > > Now after attempting to install it on both CentOS 6.4 and 6.5 it
> fails with the same error while compiling SSL support for ruby.
> >
> > >
> >
> > > Can you provide the actual error? Maybe you're missing ssl-devel
> package (I assume it should've been installed via installer already but
> maybe for some reason it wasn't?).
> >
> > >
> >
> > > Cheers
> >
> > >
> >
> > > # Piotr
> >
> >
> >
> > compiling ossl_pkey_ec.c
> >
> > ossl_pkey_ec.c: In function âossl_ec_group_initializeâ:
> >
> > ossl_pkey_ec.c:761: warning: implicit declaration of function
> âEC_GF2m_simple_me
> >
> > thodâ
> >
> > ossl_pkey_ec.c:761: warning: assignment makes pointer from integer
> without a cas
> >
> > t
> >
> > ossl_pkey_ec.c:816: error: âEC_GROUP_new_curve_GF2mâ undeclared (first
> use in th
> >
> > is function)
> >
> > ossl_pkey_ec.c:816: error: (Each undeclared identifier is reported only
> once
> >
> > ossl_pkey_ec.c:816: error: for each function it appears in.)
> >
> > make[2]: *** [ossl_pkey_ec.o] Error 1
> >
> > make[2]: Leaving directory `/usr/local/src/ruby-1.9.3-p448/ext/openssl'
> >
> > make[1]: *** [ext/openssl/all] Error 2
> >
> > make[1]: Leaving directory `/usr/local/src/ruby-1.9.3-p448'
> >
> > make: *** [build-ext] Error 2
> >
> > !!! Compiling ruby 1.9.3-p448 failed!
> >
> > Setting up chruby...
> >
> > for dir in `find etc lib bin sbin share -type d 2>/dev/null`; do mkdir
> -p /usr/l
> >
> > ocal/$dir; done
> >
> > for file in `find etc lib bin sbin share -type f 2>/dev/null`; do cp
> $file /usr/
> >
> > local/$file; done
> >
> > mkdir -p /usr/local/share/doc/chruby-0.3.6
> >
> > cp -r *.md *.txt /usr/local/share/doc/chruby-0.3.6/
> >
> > Ruby 1.9.3 installed, ready on next login/new shell.
> >
> > Make sure we are using the proper Ruby version...
> >
> > chruby: unknown Ruby: 1.9.3-p448
> >
> > Installing Puppet...
> >
> > which: no puppet in
> (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:
> >
> > /bin:/usr/sbin:/usr/bin:/root/bin)
> >
> > install-puppet.sh: line 16: gem: command not found
> >
> > Running rest of installation (with correct, newly installed Ruby)...
> >
> > Applying Puppet recipe (will take a while, please be patient)...
> >
> > ./apply_and_finalize.sh: line 12: ruby: command not found
> >
> > Installation failed.
>
> Hi Matthew. I recently came across the same error while trying out the CE
> Installer. The error apparently comes from an issue with openssl and ruby.
> To fix my issue, I did the following:
>
> 1- Run the ./install script of the ce-installer at least once (so you have
> the basic files it needs).
>
> 2- Edit "/usr/local/bin/ruby-install" by commenting out the "extract_ruby"
> line (for me, it was line 35 of the script). The reason you want to do
> this, is because you will have to edit a file which comes from the ruby
> package in the next step, and if you don't comment this out, it will simply
> get overwritten as it gets re-extracted.
>
> 3- Edit "/usr/local/src/ruby-1.9.3-p448/ext/openssl/ossl_pkey_ec.c" by
> adding the lines in green shown on the following page:
> https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/41808/diff
>  (do note you only need to edit the information from the ossl_pkey_ec.c
> code block).
>
> 4- Run the ce-installer's install script.
>
> In my case it allowed me to finish the install without any further
> complications. Hope this helps you :)
>
> --
> --
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Gitorious" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to