From owner-freebsd-current Mon Apr 13 13:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09093 for freebsd-current-outgoing; Mon, 13 Apr 1998 13:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09083 for ; Mon, 13 Apr 1998 20:24:01 GMT (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id PAA02131 for ; Mon, 13 Apr 1998 15:25:40 GMT Message-ID: <007001bd6719$7e62f620$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: Subject: Re: compiling newest wine seems to cause crash. Date: Mon, 13 Apr 1998 16:19:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >can someone on a recent -current box try compiling the latest version of >wine? > >the url to wine is: > anyhow, i don't seem to get any disk damage (which is odd on a -j# compile), but then again, the disks aren't marked clean on reboot, so it's prolly just a coincidence and i also don't have async or anything odd right now, just normal mount. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message