On Mon, 2002-11-04 at 22:00, Jan Stocker wrote: > > It'd probably be a good idea to try it again before reporting > > it as if it were still not working. It may or may not have been > > fixed by the signal and FP register state commits, etc., so just > > because it was broken doesn't mean it's broken now. > > > > Even if it *is* still broken, it could be broken in an entirely > > different way... 8-). > > It is broken with the same symtoms for the last months. > > a) FreeBSD freezes... you've to do a cold start, no keys or anything > work > b) FreeBSD reboots after a few secs of doing nothin' > c) wine / wineserver process hangs in the background, doing nothing, > consuming cpu time and cant be killed by kill -9 . > > My system is from 26. October. Not new enough? Tonight .i'll get the > newest one and recompile the newest wine and tomorrow (8.00 CET) you'll > get a dmesg / uname -a /sysctl -a for my system, i'm sure with a > non-working wine. >
We've a compile problem for wine, which should be fixed first before we con continue this thread Jan FYI: text_i386.o context_i386.c context_i386.c: In function `get_thread_context': context_i386.c:376: structure has no member named `dr0' context_i386.c:377: structure has no member named `dr1' context_i386.c:378: structure has no member named `dr2' context_i386.c:379: structure has no member named `dr3' context_i386.c:380: structure has no member named `dr6' context_i386.c:381: structure has no member named `dr7' context_i386.c: In function `set_thread_context': context_i386.c:440: structure has no member named `dr0' context_i386.c:441: structure has no member named `dr1' context_i386.c:442: structure has no member named `dr2' context_i386.c:443: structure has no member named `dr3' context_i386.c:444: structure has no member named `dr4' context_i386.c:445: structure has no member named `dr5' context_i386.c:446: structure has no member named `dr6' context_i386.c:447: structure has no member named `dr7' gmake[1]: *** [context_i386.o] Error 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
