kernel32: fix cpu detection on NetBSD

[Austin English]

On Sun, Jan 18, 2009 at 12:19 PM, David Laight <david at l8s.co.uk> wrote:
> On Sun, Jan 18, 2009 at 06:40:30PM +0100, Francois Gouget wrote:
>> On Sat, 17 Jan 2009, Austin English wrote:
>> [...]
>> > bash-3.2$ make thread.ok
>> > ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p
>> > kernel32_test.exe.so thread.c && touch thread.ok
>> > err:process:__wine_kernel_init boot event wait timed out
>> > assertion "thread->pt_blockgen == thread->pt_unblockgen" failed: file
>> > "/home/builds/ab/netbsd-4-0-1-RELEASE/src/lib/libpthread/pthread_lock.c",
>> > line 195, function "pthread_spinlock"
>> > assertion "thread->pt_blockgen == thread->pt_unblockgen" failed: file
>> > "/home/builds/ab/netbsd-4-0-1-RELEASE/src/lib/libpthread/pthread_lock.c",
>> > line 195, function "pthread_spinlock"
>> > *** Error code 1
>> >
>> > Stop.
>> > make: stopped in /home/austin/wine-git/dlls/kernel32/tests
>> >
>> > Haven't found a fix for that one yet. They've got a patch in their
>> > port to use use wine-kthread by default, but doesn't seem to help.
>>
>> Ok. That looks like another issue. Does anything run at all on NetBSD?
>
> A lot of things run on NetBSD :-)
>
> Which version of NetBSD are you testing on?
> NetBSD 4 uses an m:n thread library, so there is no guarantee which system
> LWP will run which user thread (it will change dynamically).
> (In particular when one user thread wakes another, it can be pre-empted
> entirely in userspace.)
>
> NetBSD 5 uses a 1:1 thread library due to intractable problems on SMP
> systems.
>
>        David
>
> --
> David Laight: david at l8s.co.uk
>

I've got NetBSD 4.0.1. I'll see if I can't get 5.0 installed somewhere
and try that.

-- 
-Austin