Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Dec 1996 03:25:45 -0800 (PST)
From:      asami@freebsd.org (Satoshi Asami)
To:        current@freebsd.org
Subject:   Re: weird crash
Message-ID:  <199612061125.DAA06696@silvia.HIP.Berkeley.EDU>
In-Reply-To: <199612061110.DAA06666@silvia.HIP.Berkeley.EDU> (asami@freebsd.org)

next in thread | previous in thread | raw e-mail | index | archive | help
 * 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
 :
<standard stuff>
 :
vfghostscript4/scripts/configure.batch
vfghostscript4/fonts
vfghostscript4/fonts/a010013l.pfb
 :
<all the missing files here>
 :
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612061125.DAA06696>