public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: ghostview problems ...
Date: Tue, 13 Jan 2004 15:24:00 -0000	[thread overview]
Message-ID: <40040DAC.8030104@msu.edu> (raw)
In-Reply-To: <400407DB.7090809@purdue.edu>

You need to uninstall the ghostscript package and install the 
ghostscript-x11 package.  You have to be careful to check each time that 
you run setup.exe that ghostscript is not being installed (if it is, 
just click in the "New" column until "Skip" is displayed).  This should 
really be fixed by the ghostscript maintainer so that ghostscript and 
ghostscript-x11 can both be installed at the same time, or so that 
applications can depend on a package that doesn't cause one or the other 
to be installed.  But I digress...


Harold

B. Marchand wrote:

> I just noticed something. Even though ghostview (gv) comes up and 
> appears to run I can never open a file with it. It says "Unknown device: 
> x11" when I try to open a PS or EPS file. The only difference I noticed 
> between gv in cygwin and that in linux is that the following library is 
> not available under cygwin:
> 
> /usr/lib/ghostscript/7.05/X11.so
> 
> 
> I wonder if this is the same reason why geomview won't run under cygwin. 
> In geomview's case (debug mode) I get a message saying
> 
> Warning: XmManager ClassInitialize: XmeTraitSet failed
> Error: attempt to add non-widget child "DropSiteManager" to parent 
> "Geomview" which supports only widgets.
> 
> 
> Any ideas as to what is missing for ghostview to run properly?
> 
> --B.
> 
> 


  reply	other threads:[~2004-01-13 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 14:59 B. Marchand
2004-01-13 15:24 ` Harold L Hunt II [this message]
2004-01-13 16:03 B. Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40040DAC.8030104@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).