From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with "xmgrace" graphing software in recent Cygwin installation
Date: Fri, 24 Jul 2020 07:19:57 +0200 [thread overview]
Message-ID: <b5606990-8d15-60bf-e794-7078ebe16f71@gmail.com> (raw)
In-Reply-To: <CAC7Qdh01AoAcyP5=WuoUfTUMyXQ5yhLAR6LTu5fjLpX35Hbvsw@mail.gmail.com>
On 24.07.2020 05:00, Bryan VanSchouwen via Cygwin wrote:
> Hello.
>
> I recently installed a copy of the Cygwin software package on my new
> Windows 10 laptop. However, whenever I try to access the "xmgrace"
> graphing software (by entering the command "xmgrace &" in the xterm command
> shell, as I did on my old Windows 7 laptop), I get the following error
> message:
>
> [vansc@LAPTOP-OHN2RCVM ~]$ xmgrace &
> [1] 1183
> [vansc@LAPTOP-OHN2RCVM ~]$ --> Broken or incomplete installation - read the
> FAQ!
> [1] Exit 1 xmgrace
> [vansc@LAPTOP-OHN2RCVM ~]$
>
> I tried reading the FAQ, but it was unhelpful for this particular issue.
> Does anyone have any ideas about why this might be happening?? Also, if it
> is an incomplete installation, then does anyone know what set of Cygwin
> utilities I need to install to obtain a fully-functioning copy of the
> "xmgrace" graphing software?
there is an entry about Fonts, and
a strace output shows that xmgrace is looking for type1 fonts on
/usr/share/ghostscript/fonts
/usr/share/grace/fonts/type1
in the past ghostscript provided them, but not anymore,
so I *guess* you need this workaround
install "urw-base35-fonts-legacy" package
$ cd /usr/share/grace/fonts/
$ ln -s /usr/share/X11/fonts/urw-fonts type1
the fonts looked by xgrace are :
/usr/share/grace/fonts/type1/d050000l.pfa
/usr/share/grace/fonts/type1/n019003l.pfa
/usr/share/grace/fonts/type1/n019004l.pfa
/usr/share/grace/fonts/type1/n019023l.pfa
/usr/share/grace/fonts/type1/n019024l.pfa
/usr/share/grace/fonts/type1/n021003l.pfa
/usr/share/grace/fonts/type1/n021004l.pfa
/usr/share/grace/fonts/type1/n021023l.pfa
/usr/share/grace/fonts/type1/n021024l.pfa
/usr/share/grace/fonts/type1/n022003l.pfa
/usr/share/grace/fonts/type1/n022004l.pfa
/usr/share/grace/fonts/type1/n022023l.pfa
/usr/share/grace/fonts/type1/n022024l.pfa
/usr/share/grace/fonts/type1/s050000l.pfa
and their pfb counterpart.
Regards
Marco
next prev parent reply other threads:[~2020-07-24 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 3:00 Bryan VanSchouwen
2020-07-24 5:19 ` Marco Atzeri [this message]
2020-07-24 7:56 ` Markus Hoenicka
2020-07-24 12:00 ` Ken Brown
2020-07-24 20:27 ` Marco Atzeri
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=b5606990-8d15-60bf-e794-7078ebe16f71@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).