From MAILER-DAEMON Thu May 07 09:08:32 2009
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1M23Ky-0006QO-C3
	for mharc-bug-ghostscript@gnu.org; Thu, 07 May 2009 09:08:32 -0400
Path: news.stanford.edu!headwall.stanford.edu!news.glorb.com!news2.glorb.com!postnews.google.com!t11g2000vbc.googlegroups.com!not-for-mail
From: pipitas <pipitas@googlemail.com>
Newsgroups: gnu.ghostscript.bug
Date: Thu, 7 May 2009 04:33:42 -0700 (PDT)
Organization: http://groups.google.com
Lines: 50
Message-ID: <d572bc56-4b89-4520-bc3c-bfa5d33d1deb@t11g2000vbc.googlegroups.com>
NNTP-Posting-Host: 85.214.145.231
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1241696022 26113 127.0.0.1 (7 May 2009 11:33:42
	GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 7 May 2009 11:33:42 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: t11g2000vbc.googlegroups.com; posting-host=85.214.145.231; 
	posting-account=jRn-xgoAAADYwolRn4lkOEQpAlF2KRNs
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 
	1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152;
	.NET CLR 3.5.30729),gzip(gfe),gzip(gfe)
Xref: news.stanford.edu gnu.ghostscript.bug:24540
To: bug-ghostscript@gnu.org
X-Mailman-Approved-At: Thu, 07 May 2009 09:08:30 -0400
Subject: How to find out build configuration of my currently used
	Ghostscript executable?
X-BeenThere: bug-ghostscript@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Bug reports and development for GNU GhostScript,
	the PostScript interpreter of the GNU project"
	<bug-ghostscript.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-ghostscript>,
	<mailto:bug-ghostscript-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-ghostscript>
List-Post: <mailto:bug-ghostscript@gnu.org>
List-Help: <mailto:bug-ghostscript-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-ghostscript>,
	<mailto:bug-ghostscript-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2009 11:42:04 -0000

My apologies if there is a more appropriate place to ask beginner
questions like mine. If there is, please tell me. A lot has changed
about "Ghostscript places" around the 'Net, and me essentially having
been offline most of the time for a few years, it looks like a new
planet to me ... (I'm delving more deeply into Ghostscript than I ever
have in my past active internet years, and the more my studying and
learning takes off, the more questions I'll have to ask).

I've started to re-read all of the Ghostscript documentation, starting
off with 'Use.htm'. It's a lot of material to digest, and I'm
appreciating any help I can get to make this happen more quickly (or
sometimes: happen at all).

So here is my first question:

Is there a quick way to find out which were the compiled-in defaults
and features into the Ghostscript executable I'm currently using?

I know that I can use 'gs -h' to find out:

1. supported input formats
2. available devices
3. current search path
4. if or if not the initialization files are compiled in

However, "Language.htm" in the documentation tells me about Display
Postscript: "facilities are available only if the dps feature or the
level2 feature was selected when Ghostscript was built".

The same is true for the composite font extensions: "are available
only if the compfont feature or the level2 feature was selected when
Ghostscript was built".

And more examples are to be found in the same file..

As an example for another open source program, have a look at Samba.
If you run

   smbd -b

you'll get a list of all config options that were applied when the
executable was build.

Is there any similar facility for Ghostscript that I'm not aware of
which lists me all built-in capabilies of my current gs executable?

(I know I could always try and build Ghostscript with exactly the
options I want or need. But _you_ know that in real life this is not
always feasible, and you'll just have to use what is available right
now.)

From MAILER-DAEMON Sat May 09 16:18:22 2009
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1M2t02-0003Mn-40
	for mharc-bug-ghostscript@gnu.org; Sat, 09 May 2009 16:18:22 -0400
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M2t00-0003L6-MS
	for bug-ghostscript@gnu.org; Sat, 09 May 2009 16:18:20 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M2szz-0003IW-0x
	for bug-ghostscript@gnu.org; Sat, 09 May 2009 16:18:20 -0400
Received: from [199.232.76.173] (port=58931 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M2szy-0003IM-T3
	for bug-ghostscript@gnu.org; Sat, 09 May 2009 16:18:18 -0400
Received: from rps1311.ovh.net ([91.121.197.91]:46036
	helo=mail.famille-link.fr)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <didier@famille-link.fr>) id 1M2szy-0002VE-NJ
	for bug-ghostscript@gnu.org; Sat, 09 May 2009 16:18:18 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.famille-link.fr (Postfix) with ESMTP id B03DB315D8
	for <bug-ghostscript@gnu.org>; Sat,  9 May 2009 22:17:48 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at famille-link.fr
Received: from mail.famille-link.fr ([127.0.0.1])
	by localhost (mail.famille-link.fr [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id Vw3HaKfoDnV1 for <bug-ghostscript@gnu.org>;
	Sat,  9 May 2009 22:17:47 +0200 (CEST)
Received: from neutrino.cosmos.net (pre68-4-78-225-76-33.fbx.proxad.net
	[78.225.76.33])
	by mail.famille-link.fr (Postfix) with ESMTPSA id 9CEAE315D1
	for <bug-ghostscript@gnu.org>; Sat,  9 May 2009 22:17:47 +0200 (CEST)
Date: Sat, 9 May 2009 22:18:09 +0200
From: Didier Link <didier@famille-link.fr>
To: bug-ghostscript@gnu.org
Message-ID: <20090509221809.55939cd5@neutrino.cosmos.net>
In-Reply-To: <d572bc56-4b89-4520-bc3c-bfa5d33d1deb@t11g2000vbc.googlegroups.com>
References: <d572bc56-4b89-4520-bc3c-bfa5d33d1deb@t11g2000vbc.googlegroups.com>
X-Mailer: Claws Mail 3.0.2 (GTK+ 2.14.7; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1)
Subject: Re: How to find out build configuration of my currently used
 Ghostscript executable?
X-BeenThere: bug-ghostscript@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Bug reports and development for GNU GhostScript,
	the PostScript interpreter of the GNU project"
	<bug-ghostscript.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-ghostscript>,
	<mailto:bug-ghostscript-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-ghostscript>
List-Post: <mailto:bug-ghostscript@gnu.org>
List-Help: <mailto:bug-ghostscript-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-ghostscript>,
	<mailto:bug-ghostscript-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 09 May 2009 20:18:21 -0000

LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpMZSBUaHUs
IDcgTWF5IDIwMDkgMDQ6MzM6NDIgLTA3MDAgKFBEVCksDQpwaXBpdGFzIDxwaXBpdGFzQGdvb2ds
ZW1haWwuY29tPiBhIMOpY3JpdCA6DQoNCj4gTXkgYXBvbG9naWVzIGlmIHRoZXJlIGlzIGEgbW9y
ZSBhcHByb3ByaWF0ZSBwbGFjZSB0byBhc2sgYmVnaW5uZXINCj4gcXVlc3Rpb25zIGxpa2UgbWlu
ZS4gSWYgdGhlcmUgaXMsIHBsZWFzZSB0ZWxsIG1lLiBBIGxvdCBoYXMgY2hhbmdlZA0KDQpIaSwN
Cg0KVGhlIG9ubHkgb25lIGFuc3dlciBmb3IgbWUgOiBpcyB5b3VyIGdzIGV4ZWN1dGFibGUgY3Jl
YXRlZA0KbWFudWFsbHkgb3IgaXMgaW4gYSBiaW5hcnkgcGFja2FnZSA/DQoNCklmIGl0J3MgdGhl
IGxhc3Qgb25lLCBtYXliZSB5b3UgY2FuIGZpbmQgdGhlIGNvbmZpZ3VyZSBvcHRpb25zIGluIHRo
ZQ0KcGFja2FnZSBtZXRhZGF0YS4gV2hhdCBkaXN0cmlidXRpb24geW91IHVzZSA/DQoNCkJlc3Qg
cmVnYXJkcy4NCg0KRGlkaWVyIExpbmsNCg0KLSAtLSANCkRpZGllciBMaW5rIDxkaWRpZXJAZmFt
aWxsZS1saW5rLmZyPg0KSmFiYmVyIDogZGlkaWVyX2xpbmtAamFiYmVyLmZyDQoNCkNsw6kgR1BH
IDogNzVCQUM5RUUNCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQ
RyB2Mi4wLjExIChHTlUvTGludXgpDQoNCmlFWUVBUkVDQUFZRkFrb0Y1UVFBQ2drUWt5UHdpblc2
eWU2RjZnQ2ZkTG5raDVuM0Fvc2VXZ2pZM1lyY3g0eG4NCkNHb0FtZ0pTTGVVUlFVeXBuSHE1c2Ni
NWtUTEZyQnJIDQo9eDVCZg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo=



