From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:104311] [Ruby master Bug#16674] Build issue of FreeBSD 12
Date: Wed, 16 Jun 2021 15:41:35 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-92534.20210616154135.572@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16674.20200305064518.572@ruby-lang.org
Issue #16674 has been updated by jeremyevans0 (Jeremy Evans).
Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN to 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: REQUIRED, 3.0: DONE
Status changed from Assigned to Closed
commit:78677f105df79e45dec451b56947509fc71c6f57 fixed this issue for the master branch. It was backported to 3.0 in commit:95aff214687a5e12c3eb57d056665741e734c188. Ruby 2.7 still fails due to this, so commit:78677f105df79e45dec451b56947509fc71c6f57 may need to be backported to Ruby 2.7. Ruby 2.5 is no longer supported, and 2.6 is in security maintenance mode. It appears Ruby CI for 2.6 fails on FreeBSD 12.2 due to a bison issue, before it would fail due to the DTrace issue.
I'm going to close this to trigger the backport to 2.7. I'm not sure if the lack of DTrace support on FreeBSD is considered a bug or not. Since it is optional, I assume not. However, if it is considered a bug, it should probably be submitted as a separate bug report, as this bug report is only regarding the build issue (which is fixed), not DTrace support itself.
----------------------------------------
Bug #16674: Build issue of FreeBSD 12
https://bugs.ruby-lang.org/issues/16674#change-92534
* Author: hsbt (Hiroshi SHIBATA)
* Status: Closed
* Priority: Normal
* Assignee: knu (Akinori MUSHA)
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: REQUIRED, 3.0: DONE
----------------------------------------
The current master branch and 2.7, 2.6 and 2.5 couldn't build with FreeBSD 12
see https://github.com/rbenv/ruby-build/issues/1272#issuecomment-455836665
We can build with `--disable-dtrace` flag on FreeBSD 12.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2021-06-16 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:45 [ruby-core:97370] [Ruby master Bug#16674] Build issue of FreeBSD 12 hsbt
2020-03-06 6:32 ` [ruby-core:97378] " hsbt
2020-10-06 3:18 ` [ruby-core:100304] " ngotogenome
2021-06-16 15:41 ` merch-redmine [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-92534.20210616154135.572@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).