From: nagachika00@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:99344] [Ruby master Bug#16846] Commit - win32ole: separate global variable declarations and definitions - backport?
Date: Sun, 26 Jul 2020 07:19:56 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-86738.20200726071955.11129@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16846.20200510152201.11129@ruby-lang.org
Issue #16846 has been updated by nagachika (Tomoyuki Chikanaga).
Backport changed from 2.5: DONTNEED, 2.6: REQUIRED, 2.7: REQUIRED to 2.5: DONTNEED, 2.6: REQUIRED, 2.7: DONE
ruby_2_7 43cc6997c59d2fbe3b91e91ee52faaa8749e9349 merged revision(s) a0bc3f2a1c2c98f225612101cb4e1ea1a6813546,75a0447c15a7ab017bd4240c2a9cc69b134b80b9,f1699314147bad2cf5550cc582693424fdbc2510.
----------------------------------------
Bug #16846: Commit - win32ole: separate global variable declarations and definitions - backport?
https://bugs.ruby-lang.org/issues/16846#change-86738
* Author: MSP-Greg (Greg L)
* Status: Closed
* Priority: Normal
* Backport: 2.5: DONTNEED, 2.6: REQUIRED, 2.7: DONE
----------------------------------------
The below commit fixes building win32ole using MinGW gcc 10.1.0. New Ruby releases (patch/teeny) are normally done with a current MSYS2 installation, so backporting this would be helpful for 2.5, 2.6, & 2.7. Not sure about the status of 2.5...
Commit win32ole: separate global variable declarations and definitions
https://github.com/ruby/ruby/commit/f1699314147bad2cf5550cc582693424fdbc2510
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2020-07-26 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 15:22 [ruby-core:98250] [Ruby master Misc#16846] Commit - win32ole: separate global variable declarations and definitions - backport? Greg.mpls
2020-07-26 7:19 ` nagachika00 [this message]
2021-04-04 22:58 ` [ruby-core:103217] [Ruby master Bug#16846] " usa
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-86738.20200726071955.11129@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).