On 2013/01/13 07:03, Brad Smith wrote: > On Sun, Jan 13, 2013 at 11:54:05AM +0000, Stuart Henderson wrote: > > It doesn't need to actually be built with support for threads, just to > > be linked with -lpthread. > > It doesn't but there is no point putting the effort in and not doing so. > I have run into a few Perl projects over the years that do require it.
IMO priorities for perl should be in order: - getting it linked -lpthread, or get rid of pthread wrapped functions in libc so libpthread can just be a 'normal' library - handling afresh's update to 5.14.2 (not until after 5.3 is tagged) - enabling threaded perl (probably next cycle if possible but with a bit of a delay after 5.14.2) I think they should not be mixed up as otherwise the source of any issues that show up will not be clear. > > > Once perl is built with thread support you won't need this workaround. > > > I'm not sure when this will be done though. Someone was working on this > > > some > > > time ago but I don't know how far that effort did go. > > > > Actual threaded perl support had issues on some arch. > > There were some issues with rthreads which threaded Perl exposed on > alpha but that was fixed awhile ago. AFAIK all of the other archs > were fine as is. Its about time this is fixed because this is just > getting ridiculous. yep.
