From owner-freebsd-stable  Tue Jul 18 14: 9:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [198.143.31.30])
	by hub.freebsd.org (Postfix) with ESMTP id 4D16237BB47
	for <stable@freebsd.org>; Tue, 18 Jul 2000 14:09:24 -0700 (PDT)
	(envelope-from mi@privatelabs.com)
Received: from misha.privatelabs.com (misha.privatelabs.com [198.143.31.6])
	by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id QAA22565
	for <stable@freebsd.org>; Tue, 18 Jul 2000 16:08:54 -0400
Received: (from mi@localhost)
	by misha.privatelabs.com (8.9.3/8.9.3) id RAA08113
	for stable@freebsd.org; Tue, 18 Jul 2000 17:07:06 -0400 (EDT)
	(envelope-from mi)
From: Mikhail Teterin <mi@privatelabs.com>
Message-Id: <200007182107.RAA08113@misha.privatelabs.com>
Subject: ghostscript port anyone? (clock(3) ?)
To: stable@freebsd.org
Date: Tue, 18 Jul 2000 17:07:06 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It appears, the ghostscript-6.01 port no longer builds :( The line:
	./obj/genarch ./obj/arch.h
hangs forever eating all of the available CPU (or one of the CPUs).

The  ghostscript's  clever way  of  determining  the host's  cache  size
appears to be the culprit :(

If I run the line under debugger, whenever I Ctrl-Z it, it is in memset:

	Program received signal SIGTSTP, Stopped (user).
	0x280db81f in memset () from /usr/lib/libc.so.4
	(gdb) where
	#0  0x280db81f in memset () from /usr/lib/libc.so.4
	#1  0x804a400 in buf.31 ()
	#2  0x8048a18 in main (argc=2, argv=0xbfbffb50) at ./src/genarch.c:202
	#3  0x80484f5 in _start ()

So it keeps on memset-ing the buffer forever.

Take a look at the  gs6.01/src/genarch.c:202 and the time_clear function
itself. Did our clock(3) change recently?

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message