Date: Sun, 18 Oct 1998 20:54:56 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: mathiasp@virtual-earth.de (Mathias Picker) Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: wine on current: bad system call (semsys) Message-ID: <199810182054.NAA10435@usr07.primenet.com> In-Reply-To: <199810161211.OAA02251@mp.virtual-earth.de> from "Mathias Picker" at Oct 16, 98 02:11:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> After conversion to current/elf and recompiling wine it crashes with > bad system call. A backtrace shows semsys to be the last call, and I > can see semsys in sys/syscall-hide.h. Since the port doesn't do anything > about it and it worked in -stable I guess this is a recent change ?!? > > I don't know if this is a ports or current problem, but has anyone any > idea how to fix it? I really need wine to run QuickBooks. You didn't say how the call was crashing; if it's due to a SIGSYS (this is a FreeBSD'ism; the correct POSIX dictated behaviour is to return an error from the call, and set the errno to ENOSYS), then it failed because the code implementing the system call is not in your kernel. Most likely, you need to rebuild your kernel to include the System V semaphore code (and throw in messaging and shared memory for good measure; if a programmer uses one System V specific wart, there's a good change he or she will use more). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810182054.NAA10435>