Subject: Re: pthread_creat = bad system call in macppc port, netbsd-current (well... almost current)
To: leon zadorin <leonleon77@gmail.com>
From: Michael Lorenz <macallan@netbsd.org>
List: port-macppc
Date: 03/05/2007 21:17:27
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Mar 5, 2007, at 18:33, leon zadorin wrote:

>> >> If you have a current kernel, you must have a current libpthread.so
>> >> as well.
>> >> if they are mismatched, you will have problems (like you are 
>> having).
>> >
>
>> It's in src/lib/libpthread
>
> Cool! Thanks everyone - all is fine now :-)

Please torture it a bit, threaded programs used to be a little tricky. 
I'll list a few observations and I'd like to know if it's just me or if 
others can confirm them.
For instance firefox didn't really work prior to newlock2 - it would 
either crash on startup or show a messed up user interface ( as in text 
misplaced and with wrong attributes ). Now it's rock stable ( by 
firefox standards at least ). I'm using pkgsrc/www/firefox.
Konqueror was usable but occasionally you'd get 'the process for the 
http protocol died unexpectedly' messages, usually after it was swapped 
out and back in. Just reloading the page cured it - after newlock2 I 
didn't see that again.
Things like KDE or heavily threaded gtk2 applications seem to run 
smoother but occasionally the whole machine locks up for a second or 
two, probably IO related.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRezPN8pnzkX8Yg2nAQK2rQgAitgQJ11M7i+vObLMn/CW1suCOZ5TSscs
KTFBegA5r8TO+Q/4yjLGQWKuT17IQPt4yk8gOyaDDsOQWIisyfVuR0Q72fjrxPPW
0CdY7knaYio/yy6TJ/rIT9UHiaJQaGMs2sdsR0dYkAa3uO3OlPE0rcCTmoeoeFVG
QgRt/2d/hNfsAe4KaB/7/XCGCNOnF45meGUfpZKvFhjRZnXDMyt99uajheOcOSDr
mm9LEfD5yvyPb5vWTbKqIv9QmTy8Hvytd3XmL/FNNckPEiS6J6wFDJw5f3vKHOOT
6qewJsITb+Nl5h0edMpCZcO4Ra9HYD61Ffu3mheiOshqLLhqYnK/yA==
=Qrua
-----END PGP SIGNATURE-----