On Friday 26 September 2008 10:06:22 Chase Douglas wrote: > Has anyone else tried to compile openssh against the new linuxthreads > stack? When I tried a few weeks ago it failed to compile auth-pam.c. > In that file they do some pretty wacky stuff like redefining some of > the pthread functions. Unfortunately, there doesn't seem to be a way > to get that file to build due to the way the uClibc pthread header > files are architected. So my suggestion would be to make sure that > openssh can compile against uClibc with the newer linuxthreads stack > before contemplating getting right of the older linuxthreads stack.
See, this is exactly the sort of bug report we _don't_ get unless we at least threaten to make the old one go away. At this point, it's been so long since 0.9.29 shipped that 0.9.30 is going to need a 0.9.30.1 fairly promptly, from the bug reports of people who don't try it until it ships and then find some regression snuck in over the past year and a half. We can't avoid it, we should just face up to it. Getting as many people as possible to test it before we ship is of course vital. (Mentioning -rc1 on the uClibc website might be a good idea, but the website seems to have moved out of the main archive and I have no interest in tracking down where it went.) > Also, I posted a patch to rectify a pthread fork mutex issue for > linuxthreads.old. I am not convinced that the newer linuxthreads stack > safely deals with the situation either, so porting that patch may be > wise. It shouldn't take hardly any work to do so as well. I'm guessing you're referring to: http://uclibc.org/lists/uclibc/2008-September/020110.html And yes, I'd like to have this discussion about the new linuxthreads. Possibly I should look for all svn commits to the old linuxthreads and see which ones are needed in the new one. I'll add it to the todo heap... > Thanks, > Chase Douglas Rob _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
