Feature #9579
closed
Does it work with static-linked-ext
or compiled?
method?
nobu@ruby-lang.org wrote:
Does it work with static-linked-ext
or compiled?
method?
Oops, I'll see if I can fix those.
nobu@ruby-lang.org wrote:
Does it work with static-linked-ext
or compiled?
method?
OK, I should have both of them working with a lot of new code
and pushed out an addendum patch:
http://bogomips.org/ruby.git/patch?id=84ea2b48a
git://80x24.org/ruby.git extmk-parallel-v2
Even without these patches, I get a lot of
"warning: already initialized constant" warnings when running
`make check' and that seems to cause failures...
normalperson@yhbt.net wrote:
Trivial addendum for v3 (pushed earlier, but I lost my Internet
connection before I could email).
http://bogomips.org/ruby.git/patch?id=5779e6040
git://80x24.org/ruby.git extmk-parallel-v3
5779e60 ext/extmk.rb: uniq extlibs
195e511 ext/extmk.rb: fix for static-linked-ext and compiled? usage
3029a5e ext/extmk.rb: parallelize configure
I'll squash this series together and commit in a few days unless there's
objections/bugs found. It should help productivity for developers with
fork enabled systems and gracefully fallback for systems without fork.
EXT_DEPS
doesn't look good to me.
Thanks for taking a look. I not sure what to do about EXT_DEPS.
The compiled? check is strange.
dl and tk will be gone soon, we can wait (or remove dl+tk sooner).
win32 cannot fork, so the special case there is not needed, even.
- Target version deleted (
2.2.0)
- Status changed from Open to Closed
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0