You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Geoff Macartney <ge...@gmail.com> on 2019/03/19 23:38:53 UTC
Website question
Hi all,
I made a start to adding changes to the Apache Brooklyn website to comply with Apache Foundation naming guidelines, wip is at [1].
However I’ve run into a problem trying to test it with Jekyll, which I haven’t installed on this machine up to now (it’s a MacBook Pro). I’ve added the version of Ruby that’s required (very old now, 2.1.2) via rvm, but when I run the “bundle install” per the docs at [2] I get complaints about openssl.
This is even when I install 2.1.2 with
rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
Despite requesting openssl, when I do bundle install I get
$ bundle install
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using RVM are
available at rvm.io/packages/openssl.
I’m loth to start building 2.1.2 from source just to get the openssl support, before I launch into that has anyone encountered this problem or can advise on an alternative approach?
Cheers
Geoff
[1] https://github.com/apache/brooklyn-docs/pull/280
[2] https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
Re: Website question
Posted by Geoff Macartney <ge...@gmail.com>.
Got it going in the end with much reinstalling of things, see https://github.com/apache/brooklyn-docs/pull/280. But I do think Docker is the way to go, and much easier to automate.
Geoff
Re: Website question
Posted by Geoff Macartney <ge...@gmail.com>.
Sure, sounds good - will ping you offline to chat
G
On Wed, 20 Mar 2019 at 23:15 Thomas Bouron <th...@cloudsoft.io>
wrote:
> While we are at it, it would be great to have an automatic build/push of
> the website and docs.
>
> Could pair on this if you are available Geoff?
>
> On Wed, 20 Mar 2019, 22:46 Geoff Macartney, <ge...@gmail.com>
> wrote:
>
> > Thanks all for the suggestions, I shall give it a go again with all that
> in
> > mind. Docker does sound like an attractive option too, John.
> >
> > Cheers
> > Geoff
> >
> >
> > On Wed, 20 Mar 2019 at 18:10 John McCabe <jo...@johnmccabe.net> wrote:
> >
> > > Geoff, have you tried using Docker rather than install locally.
> > >
> > > This has worked well for the OpenFaaS site -
> > >
> > >
> >
> https://github.com/openfaas/openfaas.github.io/blob/master/docker-compose.yml
> > >
> > > On Wed, Mar 20, 2019, 1:56 PM Thomas Bouron <
> thomas.bouron@cloudsoft.io>
> > > wrote:
> > >
> > > > Hey Geoff.
> > > >
> > > > I'm on the same boat as you, but I managed to recompile ruby 2.1.2
> with
> > > > open ssl using:
> > > >
> > > > rvm reinstall 2.1.2 --with-opt-dir=/usr/local
> > > > --with-openssl-dir=/usr/local/opt/openssl
> > > > (OpenSSL has been installed with brew)
> > > >
> > > > `bundle install` does not complain anymore about openssl. However, it
> > > fails
> > > > to install nokogiri even though I have the XCode CLI:
> > > >
> > > > ```
> > > > Installing nokogiri 1.6.5 with native extensions
> > > > Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
> > > >
> > > > current directory:
> > > > /Users/thomasbouron/.rvm/gems/ruby-2.1.2@brooklyn-site
> > > > /gems/nokogiri-1.6.5/ext/nokogiri
> > > > /Users/thomasbouron/.rvm/rubies/ruby-2.1.2/bin/ruby -r
> > > > ./siteconf20190320-3453-1vglirq.rb extconf.rb
> > > > checking if the C compiler accepts ... yes
> > > > checking if the C compiler accepts
> > > > -Wno-error=unused-command-line-argument-hard-error-in-future... no
> > > > Building nokogiri using packaged libraries.
> > > > -----
> > > > The file "/usr/include/iconv.h" is missing in your build environment,
> > > > which means you haven't installed Xcode Command Line Tools properly.
> > > >
> > > > To install Command Line Tools, try running `xcode-select --install`
> on
> > > > terminal and follow the instructions. If it fails, open Xcode.app,
> > > > select from the menu "Xcode" - "Open Developer Tool" - "More
> Developer
> > > > Tools" to open the developer site, download the installer for your OS
> > > > version and run it.
> > > > -----
> > > > *** extconf.rb failed ***
> > > > Could not create Makefile due to some reason, probably lack of
> > necessary
> > > > libraries and/or headers. Check the mkmf.log file for more details.
> > You
> > > > may
> > > > need configuration options.
> > > > ```
> > > >
> > > > On Wed, 20 Mar 2019 at 00:16 Peter Abramowitsch <
> > pabramowitsch@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Geoff
> > > > >
> > > > > Not that long ago I was using a much more recent ruby with openssl.
> > > > >
> > > > >
> > > > > I'm running 2.3.2 and just re-installed openssl
> > > > >
> > > > > cogitext:~ peterabramowitsch$ rvm list
> > > > > rvm rubies
> > > > > =* ruby-2.3.2 [ x86_64 ]
> > > > > # => - current
> > > > > # =* - current && default
> > > > > # * - default
> > > > >
> > > > >
> > > > > cogitext:~ peterabramowitsch$ gem list openssl
> > > > > *** LOCAL GEMS ***
> > > > > openssl (2.1.2)
> > > > >
> > > > > The gemsite can function with http or https, I think yours is an
> > issue
> > > > > with bundler which I've seen before which is caused by a kind of
> > > > > catch-22. It needs ssl to do a download of openssl which it needs
> > to
> > > > > do the download.....
> > > > >
> > > > > Fix 1.
> > > > > Change the first line of the gemfile to http:
> > > > > source 'http://rubygems.org'
> > > > > And now do a bundle install
> > > > > After a successful bundle install you might be able to change it
> back
> > > > >
> > > > > Fix 2.
> > > > > manually install openssl via "gem install openssl"
> > > > > and then your bundle install should work correctly
> > > > >
> > > > >
> > > > >
> > > > > -P.
> > > > >
> > > > > Sent from my iPad
> > > > >
> > > > >
> > > > > > On Mar 19, 2019, at 16:38, Geoff Macartney <
> > > geoff.macartney@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I made a start to adding changes to the Apache Brooklyn website
> to
> > > > > comply with Apache Foundation naming guidelines, wip is at [1].
> > > > > >
> > > > > > However I’ve run into a problem trying to test it with Jekyll,
> > which
> > > I
> > > > > haven’t installed on this machine up to now (it’s a MacBook Pro).
> > I’ve
> > > > > added the version of Ruby that’s required (very old now, 2.1.2) via
> > > rvm,
> > > > > but when I run the “bundle install” per the docs at [2] I get
> > > complaints
> > > > > about openssl.
> > > > > >
> > > > > > This is even when I install 2.1.2 with
> > > > > >
> > > > > > rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
> > > > > >
> > > > > > Despite requesting openssl, when I do bundle install I get
> > > > > >
> > > > > > $ bundle install
> > > > > > Could not load OpenSSL.
> > > > > > You must recompile Ruby with OpenSSL support or change the
> sources
> > in
> > > > > your Gemfile from 'https' to 'http'. Instructions for compiling
> with
> > > > > OpenSSL using RVM are
> > > > > > available at rvm.io/packages/openssl.
> > > > > >
> > > > > > I’m loth to start building 2.1.2 from source just to get the
> > openssl
> > > > > support, before I launch into that has anyone encountered this
> > problem
> > > or
> > > > > can advise on an alternative approach?
> > > > > >
> > > > > > Cheers
> > > > > > Geoff
> > > > > >
> > > > > > [1] https://github.com/apache/brooklyn-docs/pull/280
> > > > > > [2]
> > > > >
> > https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
> > > > > >
> > > > >
> > > > --
> > > > Thomas Bouron
> > > > Senior Software Engineer
> > > >
> > > > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > > >
> > > > GitHub: https://github.com/tbouron
> > > > Twitter: https://twitter.com/eltibouron
> > > >
> > > > Need a hand with AWS? Get a Free Consultation.
> > > >
> > >
> >
> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
Re: Website question
Posted by Thomas Bouron <th...@cloudsoft.io>.
While we are at it, it would be great to have an automatic build/push of
the website and docs.
Could pair on this if you are available Geoff?
On Wed, 20 Mar 2019, 22:46 Geoff Macartney, <ge...@gmail.com>
wrote:
> Thanks all for the suggestions, I shall give it a go again with all that in
> mind. Docker does sound like an attractive option too, John.
>
> Cheers
> Geoff
>
>
> On Wed, 20 Mar 2019 at 18:10 John McCabe <jo...@johnmccabe.net> wrote:
>
> > Geoff, have you tried using Docker rather than install locally.
> >
> > This has worked well for the OpenFaaS site -
> >
> >
> https://github.com/openfaas/openfaas.github.io/blob/master/docker-compose.yml
> >
> > On Wed, Mar 20, 2019, 1:56 PM Thomas Bouron <th...@cloudsoft.io>
> > wrote:
> >
> > > Hey Geoff.
> > >
> > > I'm on the same boat as you, but I managed to recompile ruby 2.1.2 with
> > > open ssl using:
> > >
> > > rvm reinstall 2.1.2 --with-opt-dir=/usr/local
> > > --with-openssl-dir=/usr/local/opt/openssl
> > > (OpenSSL has been installed with brew)
> > >
> > > `bundle install` does not complain anymore about openssl. However, it
> > fails
> > > to install nokogiri even though I have the XCode CLI:
> > >
> > > ```
> > > Installing nokogiri 1.6.5 with native extensions
> > > Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
> > >
> > > current directory:
> > > /Users/thomasbouron/.rvm/gems/ruby-2.1.2@brooklyn-site
> > > /gems/nokogiri-1.6.5/ext/nokogiri
> > > /Users/thomasbouron/.rvm/rubies/ruby-2.1.2/bin/ruby -r
> > > ./siteconf20190320-3453-1vglirq.rb extconf.rb
> > > checking if the C compiler accepts ... yes
> > > checking if the C compiler accepts
> > > -Wno-error=unused-command-line-argument-hard-error-in-future... no
> > > Building nokogiri using packaged libraries.
> > > -----
> > > The file "/usr/include/iconv.h" is missing in your build environment,
> > > which means you haven't installed Xcode Command Line Tools properly.
> > >
> > > To install Command Line Tools, try running `xcode-select --install` on
> > > terminal and follow the instructions. If it fails, open Xcode.app,
> > > select from the menu "Xcode" - "Open Developer Tool" - "More Developer
> > > Tools" to open the developer site, download the installer for your OS
> > > version and run it.
> > > -----
> > > *** extconf.rb failed ***
> > > Could not create Makefile due to some reason, probably lack of
> necessary
> > > libraries and/or headers. Check the mkmf.log file for more details.
> You
> > > may
> > > need configuration options.
> > > ```
> > >
> > > On Wed, 20 Mar 2019 at 00:16 Peter Abramowitsch <
> pabramowitsch@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Geoff
> > > >
> > > > Not that long ago I was using a much more recent ruby with openssl.
> > > >
> > > >
> > > > I'm running 2.3.2 and just re-installed openssl
> > > >
> > > > cogitext:~ peterabramowitsch$ rvm list
> > > > rvm rubies
> > > > =* ruby-2.3.2 [ x86_64 ]
> > > > # => - current
> > > > # =* - current && default
> > > > # * - default
> > > >
> > > >
> > > > cogitext:~ peterabramowitsch$ gem list openssl
> > > > *** LOCAL GEMS ***
> > > > openssl (2.1.2)
> > > >
> > > > The gemsite can function with http or https, I think yours is an
> issue
> > > > with bundler which I've seen before which is caused by a kind of
> > > > catch-22. It needs ssl to do a download of openssl which it needs
> to
> > > > do the download.....
> > > >
> > > > Fix 1.
> > > > Change the first line of the gemfile to http:
> > > > source 'http://rubygems.org'
> > > > And now do a bundle install
> > > > After a successful bundle install you might be able to change it back
> > > >
> > > > Fix 2.
> > > > manually install openssl via "gem install openssl"
> > > > and then your bundle install should work correctly
> > > >
> > > >
> > > >
> > > > -P.
> > > >
> > > > Sent from my iPad
> > > >
> > > >
> > > > > On Mar 19, 2019, at 16:38, Geoff Macartney <
> > geoff.macartney@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I made a start to adding changes to the Apache Brooklyn website to
> > > > comply with Apache Foundation naming guidelines, wip is at [1].
> > > > >
> > > > > However I’ve run into a problem trying to test it with Jekyll,
> which
> > I
> > > > haven’t installed on this machine up to now (it’s a MacBook Pro).
> I’ve
> > > > added the version of Ruby that’s required (very old now, 2.1.2) via
> > rvm,
> > > > but when I run the “bundle install” per the docs at [2] I get
> > complaints
> > > > about openssl.
> > > > >
> > > > > This is even when I install 2.1.2 with
> > > > >
> > > > > rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
> > > > >
> > > > > Despite requesting openssl, when I do bundle install I get
> > > > >
> > > > > $ bundle install
> > > > > Could not load OpenSSL.
> > > > > You must recompile Ruby with OpenSSL support or change the sources
> in
> > > > your Gemfile from 'https' to 'http'. Instructions for compiling with
> > > > OpenSSL using RVM are
> > > > > available at rvm.io/packages/openssl.
> > > > >
> > > > > I’m loth to start building 2.1.2 from source just to get the
> openssl
> > > > support, before I launch into that has anyone encountered this
> problem
> > or
> > > > can advise on an alternative approach?
> > > > >
> > > > > Cheers
> > > > > Geoff
> > > > >
> > > > > [1] https://github.com/apache/brooklyn-docs/pull/280
> > > > > [2]
> > > >
> https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
> > > > >
> > > >
> > > --
> > > Thomas Bouron
> > > Senior Software Engineer
> > >
> > > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> > >
> > > GitHub: https://github.com/tbouron
> > > Twitter: https://twitter.com/eltibouron
> > >
> > > Need a hand with AWS? Get a Free Consultation.
> > >
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: Website question
Posted by Geoff Macartney <ge...@gmail.com>.
Thanks all for the suggestions, I shall give it a go again with all that in
mind. Docker does sound like an attractive option too, John.
Cheers
Geoff
On Wed, 20 Mar 2019 at 18:10 John McCabe <jo...@johnmccabe.net> wrote:
> Geoff, have you tried using Docker rather than install locally.
>
> This has worked well for the OpenFaaS site -
>
> https://github.com/openfaas/openfaas.github.io/blob/master/docker-compose.yml
>
> On Wed, Mar 20, 2019, 1:56 PM Thomas Bouron <th...@cloudsoft.io>
> wrote:
>
> > Hey Geoff.
> >
> > I'm on the same boat as you, but I managed to recompile ruby 2.1.2 with
> > open ssl using:
> >
> > rvm reinstall 2.1.2 --with-opt-dir=/usr/local
> > --with-openssl-dir=/usr/local/opt/openssl
> > (OpenSSL has been installed with brew)
> >
> > `bundle install` does not complain anymore about openssl. However, it
> fails
> > to install nokogiri even though I have the XCode CLI:
> >
> > ```
> > Installing nokogiri 1.6.5 with native extensions
> > Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
> >
> > current directory:
> > /Users/thomasbouron/.rvm/gems/ruby-2.1.2@brooklyn-site
> > /gems/nokogiri-1.6.5/ext/nokogiri
> > /Users/thomasbouron/.rvm/rubies/ruby-2.1.2/bin/ruby -r
> > ./siteconf20190320-3453-1vglirq.rb extconf.rb
> > checking if the C compiler accepts ... yes
> > checking if the C compiler accepts
> > -Wno-error=unused-command-line-argument-hard-error-in-future... no
> > Building nokogiri using packaged libraries.
> > -----
> > The file "/usr/include/iconv.h" is missing in your build environment,
> > which means you haven't installed Xcode Command Line Tools properly.
> >
> > To install Command Line Tools, try running `xcode-select --install` on
> > terminal and follow the instructions. If it fails, open Xcode.app,
> > select from the menu "Xcode" - "Open Developer Tool" - "More Developer
> > Tools" to open the developer site, download the installer for your OS
> > version and run it.
> > -----
> > *** extconf.rb failed ***
> > Could not create Makefile due to some reason, probably lack of necessary
> > libraries and/or headers. Check the mkmf.log file for more details. You
> > may
> > need configuration options.
> > ```
> >
> > On Wed, 20 Mar 2019 at 00:16 Peter Abramowitsch <pabramowitsch@gmail.com
> >
> > wrote:
> >
> > > Hi Geoff
> > >
> > > Not that long ago I was using a much more recent ruby with openssl.
> > >
> > >
> > > I'm running 2.3.2 and just re-installed openssl
> > >
> > > cogitext:~ peterabramowitsch$ rvm list
> > > rvm rubies
> > > =* ruby-2.3.2 [ x86_64 ]
> > > # => - current
> > > # =* - current && default
> > > # * - default
> > >
> > >
> > > cogitext:~ peterabramowitsch$ gem list openssl
> > > *** LOCAL GEMS ***
> > > openssl (2.1.2)
> > >
> > > The gemsite can function with http or https, I think yours is an issue
> > > with bundler which I've seen before which is caused by a kind of
> > > catch-22. It needs ssl to do a download of openssl which it needs to
> > > do the download.....
> > >
> > > Fix 1.
> > > Change the first line of the gemfile to http:
> > > source 'http://rubygems.org'
> > > And now do a bundle install
> > > After a successful bundle install you might be able to change it back
> > >
> > > Fix 2.
> > > manually install openssl via "gem install openssl"
> > > and then your bundle install should work correctly
> > >
> > >
> > >
> > > -P.
> > >
> > > Sent from my iPad
> > >
> > >
> > > > On Mar 19, 2019, at 16:38, Geoff Macartney <
> geoff.macartney@gmail.com>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I made a start to adding changes to the Apache Brooklyn website to
> > > comply with Apache Foundation naming guidelines, wip is at [1].
> > > >
> > > > However I’ve run into a problem trying to test it with Jekyll, which
> I
> > > haven’t installed on this machine up to now (it’s a MacBook Pro). I’ve
> > > added the version of Ruby that’s required (very old now, 2.1.2) via
> rvm,
> > > but when I run the “bundle install” per the docs at [2] I get
> complaints
> > > about openssl.
> > > >
> > > > This is even when I install 2.1.2 with
> > > >
> > > > rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
> > > >
> > > > Despite requesting openssl, when I do bundle install I get
> > > >
> > > > $ bundle install
> > > > Could not load OpenSSL.
> > > > You must recompile Ruby with OpenSSL support or change the sources in
> > > your Gemfile from 'https' to 'http'. Instructions for compiling with
> > > OpenSSL using RVM are
> > > > available at rvm.io/packages/openssl.
> > > >
> > > > I’m loth to start building 2.1.2 from source just to get the openssl
> > > support, before I launch into that has anyone encountered this problem
> or
> > > can advise on an alternative approach?
> > > >
> > > > Cheers
> > > > Geoff
> > > >
> > > > [1] https://github.com/apache/brooklyn-docs/pull/280
> > > > [2]
> > > https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
> > > >
> > >
> > --
> > Thomas Bouron
> > Senior Software Engineer
> >
> > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
> >
> > GitHub: https://github.com/tbouron
> > Twitter: https://twitter.com/eltibouron
> >
> > Need a hand with AWS? Get a Free Consultation.
> >
>
Re: Website question
Posted by John McCabe <jo...@johnmccabe.net>.
Geoff, have you tried using Docker rather than install locally.
This has worked well for the OpenFaaS site -
https://github.com/openfaas/openfaas.github.io/blob/master/docker-compose.yml
On Wed, Mar 20, 2019, 1:56 PM Thomas Bouron <th...@cloudsoft.io>
wrote:
> Hey Geoff.
>
> I'm on the same boat as you, but I managed to recompile ruby 2.1.2 with
> open ssl using:
>
> rvm reinstall 2.1.2 --with-opt-dir=/usr/local
> --with-openssl-dir=/usr/local/opt/openssl
> (OpenSSL has been installed with brew)
>
> `bundle install` does not complain anymore about openssl. However, it fails
> to install nokogiri even though I have the XCode CLI:
>
> ```
> Installing nokogiri 1.6.5 with native extensions
> Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
>
> current directory:
> /Users/thomasbouron/.rvm/gems/ruby-2.1.2@brooklyn-site
> /gems/nokogiri-1.6.5/ext/nokogiri
> /Users/thomasbouron/.rvm/rubies/ruby-2.1.2/bin/ruby -r
> ./siteconf20190320-3453-1vglirq.rb extconf.rb
> checking if the C compiler accepts ... yes
> checking if the C compiler accepts
> -Wno-error=unused-command-line-argument-hard-error-in-future... no
> Building nokogiri using packaged libraries.
> -----
> The file "/usr/include/iconv.h" is missing in your build environment,
> which means you haven't installed Xcode Command Line Tools properly.
>
> To install Command Line Tools, try running `xcode-select --install` on
> terminal and follow the instructions. If it fails, open Xcode.app,
> select from the menu "Xcode" - "Open Developer Tool" - "More Developer
> Tools" to open the developer site, download the installer for your OS
> version and run it.
> -----
> *** extconf.rb failed ***
> Could not create Makefile due to some reason, probably lack of necessary
> libraries and/or headers. Check the mkmf.log file for more details. You
> may
> need configuration options.
> ```
>
> On Wed, 20 Mar 2019 at 00:16 Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Hi Geoff
> >
> > Not that long ago I was using a much more recent ruby with openssl.
> >
> >
> > I'm running 2.3.2 and just re-installed openssl
> >
> > cogitext:~ peterabramowitsch$ rvm list
> > rvm rubies
> > =* ruby-2.3.2 [ x86_64 ]
> > # => - current
> > # =* - current && default
> > # * - default
> >
> >
> > cogitext:~ peterabramowitsch$ gem list openssl
> > *** LOCAL GEMS ***
> > openssl (2.1.2)
> >
> > The gemsite can function with http or https, I think yours is an issue
> > with bundler which I've seen before which is caused by a kind of
> > catch-22. It needs ssl to do a download of openssl which it needs to
> > do the download.....
> >
> > Fix 1.
> > Change the first line of the gemfile to http:
> > source 'http://rubygems.org'
> > And now do a bundle install
> > After a successful bundle install you might be able to change it back
> >
> > Fix 2.
> > manually install openssl via "gem install openssl"
> > and then your bundle install should work correctly
> >
> >
> >
> > -P.
> >
> > Sent from my iPad
> >
> >
> > > On Mar 19, 2019, at 16:38, Geoff Macartney <ge...@gmail.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I made a start to adding changes to the Apache Brooklyn website to
> > comply with Apache Foundation naming guidelines, wip is at [1].
> > >
> > > However I’ve run into a problem trying to test it with Jekyll, which I
> > haven’t installed on this machine up to now (it’s a MacBook Pro). I’ve
> > added the version of Ruby that’s required (very old now, 2.1.2) via rvm,
> > but when I run the “bundle install” per the docs at [2] I get complaints
> > about openssl.
> > >
> > > This is even when I install 2.1.2 with
> > >
> > > rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
> > >
> > > Despite requesting openssl, when I do bundle install I get
> > >
> > > $ bundle install
> > > Could not load OpenSSL.
> > > You must recompile Ruby with OpenSSL support or change the sources in
> > your Gemfile from 'https' to 'http'. Instructions for compiling with
> > OpenSSL using RVM are
> > > available at rvm.io/packages/openssl.
> > >
> > > I’m loth to start building 2.1.2 from source just to get the openssl
> > support, before I launch into that has anyone encountered this problem or
> > can advise on an alternative approach?
> > >
> > > Cheers
> > > Geoff
> > >
> > > [1] https://github.com/apache/brooklyn-docs/pull/280
> > > [2]
> > https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
> > >
> >
> --
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
Re: Website question
Posted by Thomas Bouron <th...@cloudsoft.io>.
Hey Geoff.
I'm on the same boat as you, but I managed to recompile ruby 2.1.2 with
open ssl using:
rvm reinstall 2.1.2 --with-opt-dir=/usr/local
--with-openssl-dir=/usr/local/opt/openssl
(OpenSSL has been installed with brew)
`bundle install` does not complain anymore about openssl. However, it fails
to install nokogiri even though I have the XCode CLI:
```
Installing nokogiri 1.6.5 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory:
/Users/thomasbouron/.rvm/gems/ruby-2.1.2@brooklyn-site
/gems/nokogiri-1.6.5/ext/nokogiri
/Users/thomasbouron/.rvm/rubies/ruby-2.1.2/bin/ruby -r
./siteconf20190320-3453-1vglirq.rb extconf.rb
checking if the C compiler accepts ... yes
checking if the C compiler accepts
-Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
-----
The file "/usr/include/iconv.h" is missing in your build environment,
which means you haven't installed Xcode Command Line Tools properly.
To install Command Line Tools, try running `xcode-select --install` on
terminal and follow the instructions. If it fails, open Xcode.app,
select from the menu "Xcode" - "Open Developer Tool" - "More Developer
Tools" to open the developer site, download the installer for your OS
version and run it.
-----
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You
may
need configuration options.
```
On Wed, 20 Mar 2019 at 00:16 Peter Abramowitsch <pa...@gmail.com>
wrote:
> Hi Geoff
>
> Not that long ago I was using a much more recent ruby with openssl.
>
>
> I'm running 2.3.2 and just re-installed openssl
>
> cogitext:~ peterabramowitsch$ rvm list
> rvm rubies
> =* ruby-2.3.2 [ x86_64 ]
> # => - current
> # =* - current && default
> # * - default
>
>
> cogitext:~ peterabramowitsch$ gem list openssl
> *** LOCAL GEMS ***
> openssl (2.1.2)
>
> The gemsite can function with http or https, I think yours is an issue
> with bundler which I've seen before which is caused by a kind of
> catch-22. It needs ssl to do a download of openssl which it needs to
> do the download.....
>
> Fix 1.
> Change the first line of the gemfile to http:
> source 'http://rubygems.org'
> And now do a bundle install
> After a successful bundle install you might be able to change it back
>
> Fix 2.
> manually install openssl via "gem install openssl"
> and then your bundle install should work correctly
>
>
>
> -P.
>
> Sent from my iPad
>
>
> > On Mar 19, 2019, at 16:38, Geoff Macartney <ge...@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > I made a start to adding changes to the Apache Brooklyn website to
> comply with Apache Foundation naming guidelines, wip is at [1].
> >
> > However I’ve run into a problem trying to test it with Jekyll, which I
> haven’t installed on this machine up to now (it’s a MacBook Pro). I’ve
> added the version of Ruby that’s required (very old now, 2.1.2) via rvm,
> but when I run the “bundle install” per the docs at [2] I get complaints
> about openssl.
> >
> > This is even when I install 2.1.2 with
> >
> > rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
> >
> > Despite requesting openssl, when I do bundle install I get
> >
> > $ bundle install
> > Could not load OpenSSL.
> > You must recompile Ruby with OpenSSL support or change the sources in
> your Gemfile from 'https' to 'http'. Instructions for compiling with
> OpenSSL using RVM are
> > available at rvm.io/packages/openssl.
> >
> > I’m loth to start building 2.1.2 from source just to get the openssl
> support, before I launch into that has anyone encountered this problem or
> can advise on an alternative approach?
> >
> > Cheers
> > Geoff
> >
> > [1] https://github.com/apache/brooklyn-docs/pull/280
> > [2]
> https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: Website question
Posted by Peter Abramowitsch <pa...@gmail.com>.
Hi Geoff
Not that long ago I was using a much more recent ruby with openssl.
I'm running 2.3.2 and just re-installed openssl
cogitext:~ peterabramowitsch$ rvm list
rvm rubies
=* ruby-2.3.2 [ x86_64 ]
# => - current
# =* - current && default
# * - default
cogitext:~ peterabramowitsch$ gem list openssl
*** LOCAL GEMS ***
openssl (2.1.2)
The gemsite can function with http or https, I think yours is an issue
with bundler which I've seen before which is caused by a kind of
catch-22. It needs ssl to do a download of openssl which it needs to
do the download.....
Fix 1.
Change the first line of the gemfile to http:
source 'http://rubygems.org'
And now do a bundle install
After a successful bundle install you might be able to change it back
Fix 2.
manually install openssl via "gem install openssl"
and then your bundle install should work correctly
-P.
Sent from my iPad
> On Mar 19, 2019, at 16:38, Geoff Macartney <ge...@gmail.com> wrote:
>
> Hi all,
>
> I made a start to adding changes to the Apache Brooklyn website to comply with Apache Foundation naming guidelines, wip is at [1].
>
> However I’ve run into a problem trying to test it with Jekyll, which I haven’t installed on this machine up to now (it’s a MacBook Pro). I’ve added the version of Ruby that’s required (very old now, 2.1.2) via rvm, but when I run the “bundle install” per the docs at [2] I get complaints about openssl.
>
> This is even when I install 2.1.2 with
>
> rvm install 2.1.2 --with-opt-dir=/usr/local --with-openssl
>
> Despite requesting openssl, when I do bundle install I get
>
> $ bundle install
> Could not load OpenSSL.
> You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using RVM are
> available at rvm.io/packages/openssl.
>
> I’m loth to start building 2.1.2 from source just to get the openssl support, before I launch into that has anyone encountered this problem or can advise on an alternative approach?
>
> Cheers
> Geoff
>
> [1] https://github.com/apache/brooklyn-docs/pull/280
> [2] https://github.com/apache/brooklyn-docs/tree/website#workstation-setup
>