Bug #12398
closed
process.c compile broken for noMMU architectures on 2.3.x
Added by gustavoz (Gustavo Zacarias) over 8 years ago.
Updated over 8 years ago.
Description
rb_spawn_process()
in process.c tries different solutions for when fork
and/or spawnv
are/aren't available.
The last resort when both aren't is to use the system()
call which stores the value in the status
variable, which isn't declared.
It only affects 2.3.0+
Files
- Description updated (diff)
- Status changed from Open to Feedback
It seems that rb_spawn_process()
has been broken since 2.0.
I think we should drop support for such platforms, no-fork
, no-spawn
, and non-Windows.
Do you have such platforms?
BTW, what do you mean by "MMU", "memory management unit"?
- Status changed from Feedback to Closed
Applied in changeset r55091.
fix build on no-fork-spawnv platforms
- process.c (rb_execarg_commandline): build command line string
from argument vector in rb_execarg.
[ruby-core:75611] [Bug #12398]
- Backport changed from 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN to 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: REQUIRED
- Backport changed from 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: REQUIRED to 2.1: WONTFIX, 2.2: REQUIRED, 2.3: REQUIRED
- Backport changed from 2.1: WONTFIX, 2.2: REQUIRED, 2.3: REQUIRED to 2.1: WONTFIX, 2.2: REQUIRED, 2.3: DONE
ruby_2_3 r55870 merged revision(s) 55090,55091.
- Backport changed from 2.1: WONTFIX, 2.2: REQUIRED, 2.3: DONE to 2.1: DONTNEED, 2.2: DONTNEED, 2.3: DONE
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0