Feature #8270: Ruby should build without thread support (aka minix)

• Status: Assigned
• Assignee: nobu (Nobuyoshi Nakada)
• Target version: -

[eike.rb (Eike Dierks)]

I tried to ./configure ruby on Minix 3.2.1,
The configure failed, because minix does not yet implement threads.

I'd like to suggest that ruby should still build on platforms without threads.

AFAIK the language does not yet require thread support in itself,
but maybe the new GC does require it.
So we might want to look up,
where the dependencies on threading really are.

[headius (Charles Nutter)]

Minix...hard core. I haven't played with that in...20 years?

Perhaps for such a limited system you can just use an older Ruby or mruby (Matz's eMbedded Ruby)?

[nobu (Nobuyoshi Nakada)]

I have never played with it at all.
"does not yet" means there is a plan to implement?

[headius (Charles Nutter)]

nobu (Nobuyoshi Nakada) wrote:

I have never played with it at all.
"does not yet" means there is a plan to implement?

I'd be very surprised if minix ever added threads. Heck, I'm surprised minix is under any sort of development at all.

[ko1 (Koichi Sasada)]

(2013/04/16 4:04), eike.rb (Eike Dierks) wrote:

I'd like to suggest that ruby should still build on platforms without threads.

Should I spend a time for this issue?
It is easy to solve, but not in short time.

I feel it is good chance for students who want to understand OSs and
interpreters.

--
// SASADA Koichi at atdot dot net

[eike.rb (Eike Dierks)]

Thanks to everyone who responded.
Porting to Minix is only a minor target.

I suggested to the minix people that they should implement threads to get that resolved.

But obviously there's a lot of work to do
to really get ruby in the multithreaded world.
Sounds like a task for ruby3.

I already learned that it's quite hard
to get rid of the global lock
for dynamic languages.

[naruse (Yui NARUSE)]

• Target version deleted (3.0)

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned