Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!feeds.phibee-telecom.net!talisker.lacave.net!lacave.net!not-for-mail From: Martin Hansen Newsgroups: comp.lang.ruby Subject: Re: Digest::Base problem Date: Thu, 12 May 2011 08:36:08 -0500 Organization: Service de news de lacave.net Lines: 22 Message-ID: References: <44e6eed427046cccdb19c01bb85b6906@ruby-forum.com> <5cd36eefaa33f21217f8d18ae36b82ba@ruby-forum.com> NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1305207383 60847 65.111.164.187 (12 May 2011 13:36:23 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 12 May 2011 13:36:23 +0000 (UTC) In-Reply-To: X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 383065 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:4359 >> http://pastie.org/1892928 > > --with-PACKAGE is the correct one, where "PACKAGE" should be replaced > with "openssl" (so, adding the path was incorrect information on my > part). We already tried this: configure: WARNING: unrecognized options: --with-openssl Same with and without a path, and same for --with-ssl. Can we somehow test if Ruby has SSL support - without using digest - which appears to be broken? Martin -- Posted via http://www.ruby-forum.com/.