ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: andrevidic1@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:81626] [Ruby trunk Bug#13643] Cannot compile ruby 2.2.5, 2.3.3, 2.3.4 on debian stretch
Date: Fri, 09 Jun 2017 04:01:02 +0000	[thread overview]
Message-ID: <redmine.journal-65323.20170609040102.d0de6c7266899027@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13643.20170609021112@ruby-lang.org

Issue #13643 has been updated by andrevidic (Andre Vidic).


Full package list: https://gist.github.com/drej2k/d0362e8635e09d6ddbf9fca604c12c72

----------------------------------------
Bug #13643: Cannot compile ruby 2.2.5, 2.3.3, 2.3.4 on debian stretch
https://bugs.ruby-lang.org/issues/13643#change-65323

* Author: andrevidic (Andre Vidic)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.2.5, 2.3.3, 2.3.4
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
Linux debian 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux

## Summary:
1. v2.2.5, v2.3.3 fail to compile using ruby build via rbenv. They do compile manually however but without openssl. See 1) for more details
2. v2.3.4 fails to compile (git cloned from https://github.com/ruby/ruby)
3. v2.4.1 works on stretch! Successfully installed using ruby-build via rbenv

## Details:
## 1) 
### v2.2.5,ruby-build install failed. Then successfully compiled manually but with the following issues:

Failed to configure -test-/win32/console. It will not be installed.
Failed to configure -test-/win32/dln. It will not be installed.
Failed to configure -test-/win32/fd_setsize. It will not be installed.
Failed to configure openssl. It will not be installed.
Failed to configure tk. It will not be installed.
Failed to configure tk/tkutil. It will not be installed.
Failed to configure win32. It will not be installed.
Failed to configure win32ole. It will not be installed.


Full make log here: https://gist.github.com/drej2k/989b3475a538f658348da9e09c186fe3 

### v2.3.3,ruby-build install failed. Then successfully compiled manually but with the following issues:

Failed to configure openssl. It will not be installed.

Full make log here: https://gist.github.com/drej2k/30da45e342e60c72f19805b3535e0734

## 2)
### v2.3.4, failed to compile (git cloned from https://github.com/ruby/ruby)

exts.mk:118: recipe for target 'ext/openssl/all' failed
make[1]: Leaving directory '/home/deploy/ruby'
uncommon.mk:240: recipe for target 'build-ext' failed

Full make log here: https://gist.github.com/drej2k/dee78dbb0a095296d70da48fa65fbee5






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

  parent reply	other threads:[~2017-06-09  4:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-13643.20170609021112@ruby-lang.org>
2017-06-09  2:11 ` [ruby-core:81624] [Ruby trunk Bug#13643] Cannot compile ruby 2.2.5, 2.3.3, 2.3.4 on debian stretch andrevidic1
2017-06-09  4:01 ` andrevidic1 [this message]
2017-06-09  6:25 ` [ruby-core:81628] " hanmac
2017-06-09  9:58 ` [ruby-core:81635] [Ruby trunk Bug#13643][Rejected] " k

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-65323.20170609040102.d0de6c7266899027@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).