From owner-freebsd-ports  Mon May 14 16:36: 2 2001
Delivered-To: freebsd-ports@freebsd.org
Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [63.114.185.254])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3F67A37B423; Mon, 14 May 2001 16:35:59 -0700 (PDT)
	(envelope-from mi@aldan.algebra.com)
Received: from misha.privatelabs.com (root@misha.plten [10.0.0.106])
	by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id SAA15458;
	Mon, 14 May 2001 18:56:21 -0400
From: mi@aldan.algebra.com
Received: from misha.privatelabs.com (mi@localhost [127.0.0.1])
	by misha.privatelabs.com (8.11.3/8.11.1) with ESMTP id f4ENYJq14093;
	Mon, 14 May 2001 19:34:20 -0400 (EDT)
	(envelope-from mi@aldan.algebra.com)
Message-Id: <200105142334.f4ENYJq14093@misha.privatelabs.com>
Date: Mon, 14 May 2001 19:34:16 -0400 (EDT)
Reply-To: mi@aldan.algebra.com
Subject: GhostScript and JPEG
To: ports@freebsd.org
Cc: andreas@freebsd.org, ghost@aladdin.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It appears, that the only thing, that makes it necessary for GS to build
its own static version of JPEG library is the value of

	D_MAX_BLOCKS_IN_MCU

To read some JPEGs embedded in some PS files, GS needs this to be set as
64, while the default libjpeg compiles this as 10.

I'm wondering, if we should just  make our graphics/jpeg port build with
the define set to 64 and make GS use the shared -ljpeg.

This would increase the size of some arrays (of pointers or of integers)
from 10 to  64 -- con. On  the pro -- faster port  build, faster startup
usually, since libjpeg is so widely used already.

Any comments? Thanks!

	-mi



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