From: Greg.mpls@... Date: 2017-03-07T03:05:41+00:00 Subject: [ruby-core:79946] [Ruby trunk Bug#13288] mingw issues with 57789 Issue #13288 has been updated by Greg L. Thank you for looking for the problem. As mentioned, I'm very c challenged. Would it help if I did a i686 build? Looking around MSYS2, the only thing I saw that might affect things was [fix_return_size.patch](https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-libffi/fix_return_size.patch). You're probably already aware of it. The last rev of the libffi package was 2016 July. ---------------------------------------- Bug #13288: mingw issues with 57789 https://bugs.ruby-lang.org/issues/13288#change-63370 * Author: Greg L * Status: Assigned * Priority: Normal * Assignee: Shyouhei Urabe * Target version: * ruby -v: ruby 2.5.0dev (2017-03-06 trunk 57789) [x64-mingw32] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- I have been building trunk with mingw/MSYS2 for a few months. I also created packages using OpenSSL 1.1.0e and gdbm 1.10. Yesterday, I build 57782 with no major issues. Today, when I built 57789 (this commit) I had a segfault in the test-all section. the build.log was fine, and it responds to ruby -v, but I haven't tested further. I built 57782 and 57788 with no major issues. I built 57789 again, and again, the segfault occurred. The full log is at [x86_64-check.log](https://github.com/MSP-Greg/ruby-makepkg-mingw/blob/master/ruby_seg_fault/x86_64-check.log), also attached. I'm not a c type, so if there's anything else you need or would like me to check, please let me know. ---Files-------------------------------- x86_64-check.log (75 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: