Bug #6616
closedMinGW: cannot build extensions or run tests due changes in exec_arg?
Description
Hello,
Originally reported in [ruby-core:45727] due Redmine being down.
Latest trunk revision (r36154) is failing on me:
https://gist.github.com/2959908
Decided to attempt a Git bisect to determine the commit that
introduced this and which doing it found another error at r36148:
https://gist.github.com/2960374
Worker machine as 4GB of RAM (Windows 7 x64) and memory was no
exhausted during tests (monitored memory usage)
Git bisect didn't tell me precisely which commit failed since the
error happens randomly except for last commit, which happens always.
Build was made on a separate directory (build32) inside Ruby's source.
MinGW GCC 4.6.3 was used (mingw-w64) which has build successfully
everything in the past.
Entire work tree is reset on every build.
I can attribute this issue to support libraries or compiler since
those have been the same and work properly in the past revisions and
also against ruby_1_9_3 branch.
Further investigation shows the following:
configuring digest/md5
wrong argument type false (expected exec_arg)
Failed to configure digest/md5. It will not be installed.
configuring digest/rmd160
wrong argument type false (expected exec_arg)
Failed to configure digest/rmd160. It will not be installed.
configuring digest/sha1
wrong argument type false (expected exec_arg)
Failed to configure digest/sha1. It will not be installed.
configuring digest/sha2
wrong argument type false (expected exec_arg)
Failed to configure digest/sha2. It will not be installed.
configuring dl
wrong argument type false (expected exec_arg)
Failed to configure dl. It will not be installed.
Which might indicate an incompatible change with exec?
Updated by luislavena (Luis Lavena) almost 13 years ago
- Status changed from Open to Assigned
Updated by luislavena (Luis Lavena) almost 13 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100