[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
nobu@ruby-lang.org wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
matz@ruby-lang.org wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85426] [Ruby trunk Bug#14448] Build Failure - MinGW gcc 7.3.0 ~ svn 62220 - RUBY_CHECK_VA_COPY
From:
Greg.mpls@...
Date:
2018-02-06 01:07:09 UTC
List:
ruby-core #85426
Issue #14448 has been updated by MSP-Greg (Greg L).
@shyouhei,
You did use the term 'show'. The code (in total) generates all the logs and the Appveyor built title and messages. It also applies a lot of patches, mostly to the test system. The 'PKGBUILD' file is just the prepare/build/install script, with ruby scripts called before and after, and also within...
If you go to https://ci.appveyor.com/project/MSP-Greg/ruby-loco/build/417/artifacts, you can download the 'zlogs_trunk_2018-02-05_62216.7z' file and see what's output.
I need to redo the patch system, as originally I hoped that a simple 'less than' / 'greater than' version constraint would work. I've now determined that an interval system is required, and haven't decided how far to go with it. Reason being is that when questions come up as to backporting, I'd prefer to just checkout a commit locally and have it build & test. Especially if I was building back when the commit occurred. FYI, I've got all the builds saved locally, going back to early April.
Thanks,
Greg
Said simply,
----------------------------------------
Bug #14448: Build Failure - MinGW gcc 7.3.0 ~ svn 62220 - RUBY_CHECK_VA_COPY
https://bugs.ruby-lang.org/issues/14448#change-70208
* Author: MSP-Greg (Greg L)
* Status: Feedback
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.0dev (2018-02-05 trunk 62224) [x64-mingw32]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Seem to be having build failures with MinGW / gcc 7.3.0. Log shown below:
```
==> Starting build()...
ruby 2.6.0dev 2018-02-05 62230
configure: loading site script /etc/config.site
../ruby/configure: line 15109: syntax error near unexpected token `va_copy,'
../ruby/configure: line 15109: ` RUBY_CHECK_VA_COPY(va_copy, va_copy((dst),(src)))'
==> ERROR: A failure occurred in build().
Aborting...
Command exited with code 1
if "%TEST_SCRIPT%" NEQ "done
```
Thanks, Greg
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>