From owner-freebsd-current Fri Dec 6 03:26:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA05136 for current-outgoing; Fri, 6 Dec 1996 03:26:28 -0800 (PST) Received: from dfw-ix8.ix.netcom.com (dfw-ix8.ix.netcom.com [206.214.98.8]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA05122 for ; Fri, 6 Dec 1996 03:26:24 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca9-23.ix.netcom.com [204.31.231.119]) by dfw-ix8.ix.netcom.com (8.6.13/8.6.12) with ESMTP id DAA14089 for ; Fri, 6 Dec 1996 03:25:47 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id DAA06696; Fri, 6 Dec 1996 03:25:45 -0800 (PST) Date: Fri, 6 Dec 1996 03:25:45 -0800 (PST) Message-Id: <199612061125.DAA06696@silvia.HIP.Berkeley.EDU> To: current@freebsd.org In-reply-to: <199612061110.DAA06666@silvia.HIP.Berkeley.EDU> (asami@freebsd.org) Subject: Re: weird crash From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I got a strange-looking panic on our package building machine. It has * been crashing left and right due to the ahc driver problems, so this * may be related to it, but I thought I'd report it anyway 'cause it * looks quite scary. Something even scarier just happened. I was testing a new ghostscript build, and the make package failed. However, it worked the next time I tried after make clean (of course, the previous make package was immediately preceded by a make clean, I verified it with the shell's history). After looking around for the missing files, I found these: === ## find vfghostscript4 vfghostscript4 vfghostscript4/files vfghostscript4/files/md5 : : vfghostscript4/scripts/configure.batch vfghostscript4/fonts vfghostscript4/fonts/a010013l.pfb : : vfghostscript4/fonts/putri.pfa === These are to installed by the following commands: === pre-install: @tar -C ${PREFIX}/share/ghostscript -xzf ${DISTDIR}/${GS_FONTS_STD} @tar -C ${PREFIX}/share/ghostscript -xzf ${DISTDIR}/${GS_FONTS_OTHER} === As the name of this directory is "vfghostscript", there is no way PREFIX getting mixed up can cause this (of course, unless /usr/local/share/ghostscript is a symlink to this directory, but it isn't now, and I don't see how that can happen and how it can automatically recover from that situation). I have been seeing strange errors lately (e.g., make clean package not working, and a make clean package immediately following it working fine). But this is the first time I caught it red-handed (or whatever, at least I found the trace of the robbery). What do you think? There are no error messages from the SCSI driver, so I think ahc is innocent on this one. Satoshi