ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: mame@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95178] [Ruby master Bug#16194] Can not compile the recent ruby 2.6.5 release due to some openssl-related issue (see issue description)
Date: Wed, 02 Oct 2019 01:28:18 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-81812.20191002012817.d088ff90bfdcd063@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16194.20191001145751@ruby-lang.org

Issue #16194 has been updated by mame (Yusuke Endoh).


@shevegen

There is no change that seems to affect openssl or build process between ruby-2.6.4 and ruby-2.6.5.  Do you mean that you could build ruby-2.6.4 before?  Can you still build ruby-2.6.4 in your current environment?

And, are you using Linux From Scratch or something?

----------------------------------------
Bug #16194: Can not compile the recent ruby 2.6.5 release due to some openssl-related issue (see issue description)
https://bugs.ruby-lang.org/issues/16194#change-81812

* Author: shevegen (Robert A. Heiler)
* Status: Feedback
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: new ruby 2.6.5 release published today (1st october 2019)
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
I am trying to compile the latest 2.6.5 release, just released recently:

    https://ftp.ruby-lang.org/pub/ruby/2.6/ruby-2.6.5.tar.xz

I had a problem, which will be mentioned soon; but I first made sure that I do not
have this problem with ruby-2.6.4, so I believe something must have changed in
behaviour.

Here is the configure line I was using for 2.6.4:

    ./configure --prefix=/opt/ruby  --enable-debug-env --enable-load-relative --enable-frozen-string-literal-debug --enable-pthread --enable-shared --with-ext=readline,openssl,+ --disable-install-capi --disable-install-doc --disable-install-rdoc

This was just a test-configure; both "make" and "make install" finished without an error though.

I then tried with 2.6.5 with exactly the same configure option as above, and this error appeared
during **make install**:


    x86_64-linux/openssl.so: undefined symbol: EC_GROUP_new_curve_GF2m - /Depot/jjjj/ruby-2.6.5/.ext/x86_64-linux/openssl.so (LoadError)
    make: *** [uncommon.mk:371: do-install-nodoc] Error 1

My local openssl is 1.1.1c by the way (also self-compiled; I compile everything from source,
typically via help from ruby. I could try ftp://ftp.openssl.org/source/openssl-1.1.1d.tar.gz
perhaps but I have had some difficulties with openssl in the past, so I'd rather try more stable
releases of openssl than unstable ones).

Anyway, I am just reporting this here so that the ruby core team is aware of the problem. No
idea what EC_GROUP_new_curve_GF2m is, but it does not appear to occur on ruby-2.6.4.




-- 
https://bugs.ruby-lang.org/

      parent reply	other threads:[~2019-10-02  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-16194.20191001145751@ruby-lang.org>
2019-10-01 14:57 ` [ruby-core:95173] [Ruby master Bug#16194] Can not compile the recent ruby 2.6.5 release due to some openssl-related issue (see issue description) shevegen
2019-10-01 16:33 ` [ruby-core:95175] " nobu
2019-10-02  1:28 ` mame [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-81812.20191002012817.d088ff90bfdcd063@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).