[OS X TeX] MacOSX-TeX Digest, Vol 156, Issue 21

Jennifer A Adams adamsjennifer2017 at gmail.com
Mon Oct 26 14:08:40 CET 2020


unsubscribe

Thank you,
Jennifer A. Adams, MPA
ASPA, IAEM, PAA
330.415.2503
http://www.jenniferaadams.com

*** please consider the environment before printing this email


From: MacOSX-TeX <macosx-tex-bounces at email.esm.psu.edu> on behalf of "macosx-tex-request at email.esm.psu.edu" <macosx-tex-request at email.esm.psu.edu>
Reply-To: "macosx-tex at email.esm.psu.edu" <macosx-tex at email.esm.psu.edu>
Date: Friday, October 23, 2020 at 3:00 PM
To: "macosx-tex at email.esm.psu.edu" <macosx-tex at email.esm.psu.edu>
Subject: MacOSX-TeX Digest, Vol 156, Issue 21

Send MacOSX-TeX mailing list submissions to
                macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>

To subscribe or unsubscribe via the World Wide Web, visit
                https://email.esm.psu.edu/mailman/listinfo/macosx-tex
or, via email, send a message with subject or body 'help' to
                macosx-tex-request at email.esm.psu.edu<mailto:macosx-tex-request at email.esm.psu.edu>

You can reach the person managing the list at
                macosx-tex-owner at email.esm.psu.edu<mailto:macosx-tex-owner at email.esm.psu.edu>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MacOSX-TeX digest..."


Today's Topics:

   1. Re: dvisvgm and ghostscript (Ettore Aldrovandi)
   2. Re: dvisvgm and ghostscript (Herbert Schulz)
   3. Re: dvisvgm and ghostscript (koch at math.uoregon.edu<mailto:koch at math.uoregon.edu>)
   4. Re: dvisvgm and ghostscript (Ettore Aldrovandi)
   5. Re: dvisvgm and ghostscript (Herbert Schulz)
   6. Re: [OFF-TOPIC] python (Doris Behrendt) (David Goldenberg)
   7. Re: dvisvgm and ghostscript (Ettore Aldrovandi)
   8. Re: dvisvgm and ghostscript (koch at uoregon.edu<mailto:koch at uoregon.edu>)
   9. Re: dvisvgm and ghostscript (Doris Behrendt)
  10. Re: dvisvgm and ghostscript (Doris Behrendt)
  11. Re: dvisvgm and ghostscript (koch at uoregon.edu<mailto:koch at uoregon.edu>)
  12. Re: dvisvgm and ghostscript (Doris Behrendt)
  13. Re: dvisvgm and ghostscript (Ettore Aldrovandi)
  14. Re: dvisvgm and ghostscript (koch at uoregon.edu<mailto:koch at uoregon.edu>)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Oct 2020 15:08:29 -0400
From: Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <4CEEC1D2-B416-4516-B425-3D43FFC70B72 at math.fsu.edu<mailto:4CEEC1D2-B416-4516-B425-3D43FFC70B72 at math.fsu.edu>>
Content-Type: text/plain; charset="utf-8"

Most likely .bash_profile is not the right startup file for that variable, because it?s only read by login shell. Try putting the same export command in .bashrc, open a new instance (new window or tab) of terminal and see if it works.

Hope this helps

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 13:18, Doris Behrendt via MacOSX-TeX <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>> wrote:

Hi all,

I want to export a tikz graphic to svg as described in the tikz manual. I?m on 10.15.7 and TeXLive 2020; I installed Ghostscript 9.53.3 from Dick Kochs Website, with the libgs.dylib.9.53 file included;

I have the following line

export LIBGS="/usr/local/share/ghostscript/9.53.3/lib/libgs.dylib.9.53?

in my .bash_profile. When I call

dvisvgm myfile.dvi


the following error message shows up:

processing of PostScript specials is disabled (Ghostscript not found)

It seems I have to use the option ?libgs=? explicitly, but how?

dvisvgm --libgs=LIBGS myfile.dvi throws the same error; also does
dvisvgm --libgs="/usr/local/share/ghostscript/9.53.3/lib/libgs.dylib.9.53" myfile.dvi

when I check the path via echo $LIBGS the path from above is printed.


Can somebody give me a hint what I?m overseeing?



Doris
----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201022/12bf0674/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 22 Oct 2020 14:17:13 -0500
From: Herbert Schulz <herbs at wideopenwest.com<mailto:herbs at wideopenwest.com>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <24C3EA6D-3797-43E9-ABE6-780639B7CBEE at wideopenwest.com<mailto:24C3EA6D-3797-43E9-ABE6-780639B7CBEE at wideopenwest.com>>
Content-Type: text/plain;              charset=utf-8

On Oct 22, 2020, at 2:08 PM, Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>> wrote:

Most likely .bash_profile is not the right startup file for that variable, because it?s only read by login shell. Try putting the same export command in .bashrc, open a new instance (new window or tab) of terminal and see if it works.

Hope this helps

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 13:18, Doris Behrendt via MacOSX-TeX <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>> wrote:

Hi all,

I want to export a tikz graphic to svg as described in the tikz manual. I?m on 10.15.7 and TeXLive 2020; I installed Ghostscript 9.53.3 from Dick Kochs Website, with the libgs.dylib.9.53 file included;

I have the following line

export LIBGS="/usr/local/share/ghostscript/9.53.3/lib/libgs.dylib.9.53?

in my .bash_profile. When I call

dvisvgm myfile.dvi


the following error message shows up:

processing of PostScript specials is disabled (Ghostscript not found)

It seems I have to use the option ?libgs=? explicitly, but how?

dvisvgm --libgs=LIBGS myfile.dvi throws the same error; also does
dvisvgm --libgs="/usr/local/share/ghostscript/9.53.3/lib/libgs.dylib.9.53" myfile.dvi

when I check the path via echo $LIBGS the path from above is printed.


Can somebody give me a hint what I?m overseeing?



Doris

Howdy,

Hmmm... if you're using the default shell in Catalina, zsh, .bash_profile, .bashrc and .profile won't be read be default even when using Terminal which is a login shell.

But the direct use as Dick Koch mentioned should still work fine. I've checked it on mys system and I successfully converted a pdf to svg.

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)



------------------------------

Message: 3
Date: Thu, 22 Oct 2020 12:19:03 -0700
From: koch at math.uoregon.edu<mailto:koch at math.uoregon.edu>
To: TeX on Mac OS X <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <A6E049DA-81A8-47BD-8C14-D0C9A732A426 at math.uoregon.edu<mailto:A6E049DA-81A8-47BD-8C14-D0C9A732A426 at math.uoregon.edu>>
Content-Type: text/plain;              charset=us-ascii

Ettore has been giving good advice on this list recently! However, in this case Doris called dvisvgm by giving it the location of the ghostscript library directly, so PATH variables ought to be irrelevant.

Doris, when you reported the command to us, you used quotation marks around the library path. When I tried this on my machine, I did not use those quotation marks. Did you retry the command by just copying my command and pasting?
Did you look into the location and make sure the library is there?

If so, I give up. After all, I created the install package and I installed on my machine running Catalina and we are running exactly the same command.

Richard Koch




------------------------------

Message: 4
Date: Thu, 22 Oct 2020 17:04:09 -0400
From: Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <83067D13-278B-455B-B0EC-BEA8BAF01255 at math.fsu.edu<mailto:83067D13-278B-455B-B0EC-BEA8BAF01255 at math.fsu.edu>>
Content-Type: text/plain; charset="utf-8"

The quotes are probably not important, but Dick is right, this may not be a PATH issue at all, rather:

The library name could be incorrect, as it may depend on how ghostscript was installed. Actually, /usr/local/share is a strange location for holding shared libraries. On my system the location is:

                /opt/brw/lib//opt/brw/lib/libgs.9.53.dylib

Don?t mind the /opt/brw prefix and replace it with /usr/local. The library name is also different, which may be also an issue here. Taking this difference into account, I was able to run Dick?s example on one of my pdf files.

So, Doris, check for these differences and see if you can run Dick?s example then.

Then there is the separate question of which is the appropriate location for the shell variable to hold the library name to export to the environment. But that is a separate issue.

Hope this helps,

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 15:19, koch at math.uoregon.edu<mailto:koch at math.uoregon.edu> wrote:

Ettore has been giving good advice on this list recently! However, in this case Doris called dvisvgm by giving it the location of the ghostscript library directly, so PATH variables ought to be irrelevant.

Doris, when you reported the command to us, you used quotation marks around the library path. When I tried this on my machine, I did not use those quotation marks. Did you retry the command by just copying my command and pasting?
Did you look into the location and make sure the library is there?

If so, I give up. After all, I created the install package and I installed on my machine running Catalina and we are running exactly the same command.

Richard Koch


----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201022/6a34998b/attachment-0001.htm>

------------------------------

Message: 5
Date: Thu, 22 Oct 2020 16:14:32 -0500
From: Herbert Schulz <herbs at wideopenwest.com<mailto:herbs at wideopenwest.com>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <E1C0BD50-FAB1-4C72-BCE3-43D5F12D45A3 at wideopenwest.com<mailto:E1C0BD50-FAB1-4C72-BCE3-43D5F12D45A3 at wideopenwest.com>>
Content-Type: text/plain;              charset=utf-8

On Oct 22, 2020, at 4:04 PM, Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>> wrote:

The quotes are probably not important, but Dick is right, this may not be a PATH issue at all, rather:

The library name could be incorrect, as it may depend on how ghostscript was installed. Actually, /usr/local/share is a strange location for holding shared libraries. On my system the location is:

           /opt/brw/lib//opt/brw/lib/libgs.9.53.dylib

Don?t mind the /opt/brw prefix and replace it with /usr/local. The library name is also different, which may be also an issue here. Taking this difference into account, I was able to run Dick?s example on one of my pdf files.

So, Doris, check for these differences and see if you can run Dick?s example then.

Then there is the separate question of which is the appropriate location for the shell variable to hold the library name to export to the environment. But that is a separate issue.

Hope this helps,

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 15:19, koch at math.uoregon.edu<mailto:koch at math.uoregon.edu> wrote:

Ettore has been giving good advice on this list recently! However, in this case Doris called dvisvgm by giving it the location of the ghostscript library directly, so PATH variables ought to be irrelevant.

Doris, when you reported the command to us, you used quotation marks around the library path. When I tried this on my machine, I did not use those quotation marks. Did you retry the command by just copying my command and pasting?
Did you look into the location and make sure the library is there?

If so, I give up. After all, I created the install package and I installed on my machine running Catalina and we are running exactly the same command.

Richard Koch

Howdy,

The path posted by Dick Koch is correct when using the installer provided by him which was also used by Doris.

Along with Dick I am baffled since his command line works fine for me (acting on a different pdf and producing a different svg.

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)



------------------------------

Message: 6
Date: Thu, 22 Oct 2020 21:21:30 +0000
From: David Goldenberg <Goldenberg at biology.utah.edu<mailto:Goldenberg at biology.utah.edu>>
To: "macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>" <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] [OFF-TOPIC] python (Doris Behrendt)
Message-ID: <CCD2435C-9966-4227-84B2-AF076EC771A1 at umail.utah.edu<mailto:CCD2435C-9966-4227-84B2-AF076EC771A1 at umail.utah.edu>>
Content-Type: text/plain; charset="utf-8"

Just a few more comments on this off-topic topic:

1. I agree that installing Anaconda is a great way to have a full Python installation with lots of trimmings. Think of it as TexLive for Python. One of the best things that Anaconda includes is the Jupyter browser-based notebook. It?s great for learning and interactive work.

2. The is clash between MacOS Mojave and Python versions later than 3.7.0, at least with the version installed with Anaconda. This breaks any of the Python features that use TKinter, including the IDLE development environment and the turtles module, for turtle graphics.  My understanding is that the clash is fixed in Catalina, but I haven?t tested it myself.

For Mojave, the last version Anaconda that seems to play well with Mojave is:
Anaconda3-5.3.1-MacOSX-x86 64.pkg
You can find an archive of all of the Anaconda installers at:
https://repo.anaconda.com/archive/

3. For a great introduction to Python and programming, I highly recommed:
Downey, A. (2017). Think Python: How to Think Like a Computer Scientist. O?Reilly, 2nd edition. http://greenteapress.com/wp/think-python-2e/

This is a short well-written book with very good exercises. It is available as both an O?Reilly paperback (on the expensive side) or as a free (as in beer) pdf!

David Goldenberg
--
School of Biological Sciences
University of Utah
257 South 1400 East
Salt Lake City, UT  84112-0840

Telephone: (801) 581-3885
Fax:  (801) 581-2174

E-mail: goldenberg at biology.utah.edu<mailto:goldenberg at biology.utah.edu>
Web page: http://goldenberg.biology.utah.edu

----------------------------------------------------------------------

Message: 1
Date: Wed, 21 Oct 2020 20:11:33 +0100
From: Luis Sequeira <lfsequeira at gmail.com<mailto:lfsequeira at gmail.com>>
To: TeX on Mac OS X Mailing List <MacOSX-TeX at email.esm.psu.edu<mailto:MacOSX-TeX at email.esm.psu.edu>>
Subject: Re: [OS X TeX] [OFF-TOPIC] python
Message-ID: <D5159A06-EC7C-48C9-86BC-36DE93483547 at gmail.com<mailto:D5159A06-EC7C-48C9-86BC-36DE93483547 at gmail.com>>
Content-Type: text/plain;        charset=us-ascii

A big +1 on the Anaconda distribution.

Completely separate from the old python 2.7 that still ships with Catalina.

Not only it includes most of the packages that you may want to use, like numpy, scipy, sympy, pandas, etc - and you can easily install any others with conda - but it also includes Jupyter Notebook, and a full Python IDE, Spyder, and more (even R Studio, if that is your cup of tea).

Also, it is easy to create separate python environments, so if you want you can test stuff in python 3.8 or 3.9, or run old packages with python 3.5, say, all very seamlessly.

LS

------------------------------


------------------------------

Message: 7
Date: Thu, 22 Oct 2020 18:08:05 -0400
From: Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <7B730E0C-40F6-4403-882C-0895EEA0EB72 at math.fsu.edu<mailto:7B730E0C-40F6-4403-882C-0895EEA0EB72 at math.fsu.edu>>
Content-Type: text/plain; charset="utf-8"

I?m baffled too. I think I have a possible explanation for the first error, but not the second, reproducing Dick?s exact command line.

For what is worth: apparently dvisvgm needs to be told the location of ghostscript?s dylib. This happens by using the command line flag ?libgs or setting the env variable LIBGS (the former overrides the latter). Also apparently dvisvgm does not find libgs.dylib by itself if not told in one of those two ways. Now, at the beginning, if the variable LIBGS, although set in .bash_profile was not picked up, it would have explained the failure, with the caveat that the error message was different.

Just for clarification, Terminal does not run a login shell, unless set in its preferences.

But all this does not explain the error once dvisvgm is run with the correct path put on the command line via ?libgs.

Most of those dylib files are actually symlinks. Is is it possible there?s a problem there? Maybe something went wrong during installation? This is what I have, but I installed ghostscript differently:

albemuth:~/tmp> ls -l /opt/brw/Cellar/ghostscript/9.53.3/lib
total 26584
-r--r--r--  1 ealdrov  wheel  13610904 Oct  2 07:59 libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.9.dylib@ -> libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.dylib@ -> libgs.9.53.dylib


?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 17:14, Herbert Schulz <herbs at wideopenwest.com<mailto:herbs at wideopenwest.com>> wrote:

On Oct 22, 2020, at 4:04 PM, Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>> wrote:

The quotes are probably not important, but Dick is right, this may not be a PATH issue at all, rather:

The library name could be incorrect, as it may depend on how ghostscript was installed. Actually, /usr/local/share is a strange location for holding shared libraries. On my system the location is:

     /opt/brw/lib//opt/brw/lib/libgs.9.53.dylib

Don?t mind the /opt/brw prefix and replace it with /usr/local. The library name is also different, which may be also an issue here. Taking this difference into account, I was able to run Dick?s example on one of my pdf files.

So, Doris, check for these differences and see if you can run Dick?s example then.

Then there is the separate question of which is the appropriate location for the shell variable to hold the library name to export to the environment. But that is a separate issue.

Hope this helps,

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu

On Oct 22, 2020, at 15:19, koch at math.uoregon.edu<mailto:koch at math.uoregon.edu> wrote:

Ettore has been giving good advice on this list recently! However, in this case Doris called dvisvgm by giving it the location of the ghostscript library directly, so PATH variables ought to be irrelevant.

Doris, when you reported the command to us, you used quotation marks around the library path. When I tried this on my machine, I did not use those quotation marks. Did you retry the command by just copying my command and pasting?
Did you look into the location and make sure the library is there?

If so, I give up. After all, I created the install package and I installed on my machine running Catalina and we are running exactly the same command.

Richard Koch

Howdy,

The path posted by Dick Koch is correct when using the installer provided by him which was also used by Doris.

Along with Dick I am baffled since his command line works fine for me (acting on a different pdf and producing a different svg.

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)

----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201022/ca6eb6e2/attachment-0001.htm>

------------------------------

Message: 8
Date: Thu, 22 Oct 2020 15:45:56 -0700
From: "koch at uoregon.edu<mailto:koch at uoregon.edu>" <koch at uoregon.edu<mailto:koch at uoregon.edu>>
To: TeX on Mac OS X <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <BC439C78-EE82-47B4-B762-C705A075D35A at uoregon.edu<mailto:BC439C78-EE82-47B4-B762-C705A075D35A at uoregon.edu>>
Content-Type: text/plain; charset="utf-8"

Most of those dylib files are actually symlinks. Is is it possible there?s a problem there? Maybe something went wrong during installation? This is what I have, but I installed ghostscript differently:

albemuth:~/tmp> ls -l /opt/brw/Cellar/ghostscript/9.53.3/lib
total 26584
-r--r--r--  1 ealdrov  wheel  13610904 Oct  2 07:59 libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.9.dylib@ -> libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.dylib@ -> libgs.9.53.dylib


?Ettore

Folks,

When Ghostscript is compiled from source, the usual

                ./configure
                make
                sudo make install

sequence does not create or install the ghostscript library. The library is created with a special command

                make so

and three files are then placed in the folder sobin inside the source directory. Two are symbolic links,

                libgs.dylib
                libgs.dylib.9

and one is an actual library,

                libgs.dylib.9.53

Then there arises the issue of where these three files should be placed. For TeX Live this issue is not very important since only one binary, dvisvgm, uses the library.

MacTeX very deliberately installs nothing in /usr/local/lib because I don'r want to interfere with libraries the user might install there from other places. The Ghostscript install

                sudo make install

places the gs binary and many other scripts in /usr/local/bin, but installs everything else in

                /usr/local/share/ghostscript/9.53.3

and this folder even contains a subfolder named lib. So that seemed to be a natural place to put the actual dynamic library.

As for symbolic links, I decided to break my own rule and add three links to /usr/local/lib named

                libgs.dylib
                libgs.9.dylib
                libgs.9.53.dylib

I am not wedded to this final piece of the puzzle. Indeed I'd much rather install nothing in /usr/local/lib. And the few people who actually use dvisvgm seem to use the flag and point to the actual location of the library.

All of this does nothing to explain the problem Doris is having. ( Incidentally, I wonder what would happen if she installed our 9.50 package instead, since it also installs a library. After that test, 9.53.3 can be installed again and it will become active.)

I'm just trying to warn us not to get involved with side issues. I hope it helps to know exactly what our package does.

Dick Koch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201022/53c707c1/attachment-0001.htm>

------------------------------

Message: 9
Date: Fri, 23 Oct 2020 05:45:56 +0200
From: Doris Behrendt <doris.behrendt at me.com<mailto:doris.behrendt at me.com>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <1E5B9BFF-6C63-4B83-ADEE-F1B4C27EAEAB at me.com<mailto:1E5B9BFF-6C63-4B83-ADEE-F1B4C27EAEAB at me.com>>
Content-Type: text/plain;              charset=utf-8

Hi all,

thanks for all the fish. I?ll read your suggestions, try them out this afternoon and keep you up to date  with my funny problem ;-)

Doris

On 23. Oct 2020, at 00:45, koch at uoregon.edu<mailto:koch at uoregon.edu> wrote:

Most of those dylib files are actually symlinks. Is is it possible there?s a problem there? Maybe something went wrong during installation? This is what I have, but I installed ghostscript differently:

albemuth:~/tmp> ls -l /opt/brw/Cellar/ghostscript/9.53.3/lib
total 26584
-r--r--r--  1 ealdrov  wheel  13610904 Oct  2 07:59 libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.9.dylib@ -> libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.dylib@ -> libgs.9.53.dylib


?Ettore

Folks,

When Ghostscript is compiled from source, the usual

           ./configure
           make
           sudo make install

sequence does not create or install the ghostscript library. The library is created with a special command

           make so

and three files are then placed in the folder sobin inside the source directory. Two are symbolic links,

           libgs.dylib
           libgs.dylib.9

and one is an actual library,

           libgs.dylib.9.53

Then there arises the issue of where these three files should be placed. For TeX Live this issue is not very important since only one binary, dvisvgm, uses the library.

MacTeX very deliberately installs nothing in /usr/local/lib because I don'r want to interfere with libraries the user might install there from other places. The Ghostscript install

           sudo make install

places the gs binary and many other scripts in /usr/local/bin, but installs everything else in

           /usr/local/share/ghostscript/9.53.3

and this folder even contains a subfolder named lib. So that seemed to be a natural place to put the actual dynamic library.

As for symbolic links, I decided to break my own rule and add three links to /usr/local/lib named

           libgs.dylib
           libgs.9.dylib
           libgs.9.53.dylib

I am not wedded to this final piece of the puzzle. Indeed I'd much rather install nothing in /usr/local/lib. And the few people who actually use dvisvgm seem to use the flag and point to the actual location of the library.

All of this does nothing to explain the problem Doris is having. ( Incidentally, I wonder what would happen if she installed our 9.50 package instead, since it also installs a library. After that test, 9.53.3 can be installed again and it will become active.)

  I'm just trying to warn us not to get involved with side issues. I hope it helps to know exactly what our package does.

Dick Koch
----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex



------------------------------

Message: 10
Date: Fri, 23 Oct 2020 17:23:12 +0200
From: Doris Behrendt <doris.behrendt at me.com<mailto:doris.behrendt at me.com>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <C984A8C5-AF69-4146-A7BD-18E362A42D2D at me.com<mailto:C984A8C5-AF69-4146-A7BD-18E362A42D2D at me.com>>
Content-Type: text/plain;              charset=utf-8

Hi all,

I repeated the process (hoping that everything just is overwritten and not having to uninstall the ghostscript stuff).

This is the command I entered and the error I got:

dvisvgm --libgs=/usr/local/share/ghostscript/9.53.3/lib/libgs.dylib.9.53 --pdf ct-logo.pdf
ERROR: Ghostscript is required to process PDF files


This is the output of my terminal in the dir named lib:

(base) Doriss-Mac-mini:lib bd$ ls -l l*
-rw-r--r--  1 root  wheel      1468 Oct  7 01:37 landscap.ps
-rwxr-xr-x  1 root  wheel  18259520 Oct  7 02:28 libgs.dylib.9.53
-rw-r--r--  1 root  wheel      3736 Oct  7 01:37 lines.ps
(base) Doriss-Mac-mini:lib bd$ pwd
/usr/local/share/ghostscript/9.53.3/lib
(base) Doriss-Mac-mini:lib bd$


The output of list at least shows that there is no symbolic link, but the file is there.


And I found ONE strange thing:
The name of the package I downloaded ends with >>?53.3<<, but the header line of the Installer window ends with >>...53.2-Full<<.

The typo .2 instead of .3 could occur also in other places, right?
Can this be connected to the reason for my problems?


Doris

On 23. Oct 2020, at 00:45, koch at uoregon.edu<mailto:koch at uoregon.edu> wrote:

Most of those dylib files are actually symlinks. Is is it possible there?s a problem there? Maybe something went wrong during installation? This is what I have, but I installed ghostscript differently:

albemuth:~/tmp> ls -l /opt/brw/Cellar/ghostscript/9.53.3/lib
total 26584
-r--r--r--  1 ealdrov  wheel  13610904 Oct  2 07:59 libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.9.dylib@ -> libgs.9.53.dylib
lrwxr-xr-x  1 ealdrov  wheel        16 Oct  2 07:59 libgs.dylib@ -> libgs.9.53.dylib


?Ettore

Folks,

When Ghostscript is compiled from source, the usual

           ./configure
           make
           sudo make install

sequence does not create or install the ghostscript library. The library is created with a special command

           make so

and three files are then placed in the folder sobin inside the source directory. Two are symbolic links,

           libgs.dylib
           libgs.dylib.9

and one is an actual library,

           libgs.dylib.9.53

Then there arises the issue of where these three files should be placed. For TeX Live this issue is not very important since only one binary, dvisvgm, uses the library.

MacTeX very deliberately installs nothing in /usr/local/lib because I don'r want to interfere with libraries the user might install there from other places. The Ghostscript install

           sudo make install

places the gs binary and many other scripts in /usr/local/bin, but installs everything else in

           /usr/local/share/ghostscript/9.53.3

and this folder even contains a subfolder named lib. So that seemed to be a natural place to put the actual dynamic library.

As for symbolic links, I decided to break my own rule and add three links to /usr/local/lib named

           libgs.dylib
           libgs.9.dylib
           libgs.9.53.dylib

I am not wedded to this final piece of the puzzle. Indeed I'd much rather install nothing in /usr/local/lib. And the few people who actually use dvisvgm seem to use the flag and point to the actual location of the library.

All of this does nothing to explain the problem Doris is having. ( Incidentally, I wonder what would happen if she installed our 9.50 package instead, since it also installs a library. After that test, 9.53.3 can be installed again and it will become active.)

  I'm just trying to warn us not to get involved with side issues. I hope it helps to know exactly what our package does.

Dick Koch
----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex



------------------------------

Message: 11
Date: Fri, 23 Oct 2020 09:13:46 -0700
From: "koch at uoregon.edu<mailto:koch at uoregon.edu>" <koch at uoregon.edu<mailto:koch at uoregon.edu>>
To: TeX on Mac OS X <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <B057C05A-BB94-4BA1-B265-DEC03EBFFD0D at uoregon.edu<mailto:B057C05A-BB94-4BA1-B265-DEC03EBFFD0D at uoregon.edu>>
Content-Type: text/plain; charset="us-ascii"

Doris,

I confirmed that my install package puts up a line about Ghostscript 9.53.2 during installation. That is my error, but unfortunately irrelevant and just a spelling error.

Just to check, I removed the entire directory /usr/local/share/ghostscript/9.53.3 from my computer and then reinstalled using the "slightly defective" package. It added 9.53.3 back to the directory.

Then I ran the test of the dvisvgm that I had done earlier. But this time I copied your command out of the latest email and just changed the name of the pdf being converted. The command ran fine.

So the puzzle remains.

I'd like you to do one final test.

                https://pages.uoregon.edu/koch <https://pages.uoregon.edu/koch>

download and install Ghostscript 9,50 Full and install it. No need to erase anything first. Then run the test again, this time changing 9.53.3 to 9.50 in appropriate places. Does this work for you?

You can easily return to 9,.53.3 by just installing it again afterward.

Dick Koch

PS: Another test would be to try to convert some other pdf illustration. The dvisvgm error message strongly suggests that this test will also fail, but just to be sure ....


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201023/e59c4e50/attachment-0001.htm>

------------------------------

Message: 12
Date: Fri, 23 Oct 2020 19:53:16 +0200
From: Doris Behrendt <doris.behrendt at me.com<mailto:doris.behrendt at me.com>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <D91AD0C0-453F-4BCB-9E52-0ADD3A0DED90 at me.com<mailto:D91AD0C0-453F-4BCB-9E52-0ADD3A0DED90 at me.com>>
Content-Type: text/plain;              charset=utf-8

Hi Dick and others,


So the puzzle remains.

I'd like you to do one final test.

           https://pages.uoregon.edu/koch

download and install Ghostscript 9,50 Full and install it. No need to erase anything first. Then run the test again, this time changing 9.53.3 to 9.50 in appropriate places. Does this work for you?



I?ll do that. But meanwhile I tried alternatives and wanted to let you know what I came up with and what problem occurred on the way:

install ghostscript via brew

(base) Doriss-Mac-mini:logo bd$ brew link --overwrite ghostscript
Linking /usr/local/Cellar/ghostscript/9.53.3...
Error: Could not symlink share/doc/ghostscript/9.53.3/API.htm
/usr/local/share/doc/ghostscript/9.53.3 is not writable.


So, following this link https://apple.stackexchange.com/questions/192227/how-to-make-files-in-usr-local-writable-for-homebrew

I had to temporarily change the ownership of the folder /urs/local

I changed from root:wheel to me:staff and after I did this, the linking went through:

brew link --overwrite ghostscript
Linking /usr/local/Cellar/ghostscript/9.53.3... 568 symlinks created

after this, I could finally run

dvisvgm --libgs=/usr/local/Cellar/ghostscript/9.53.3/lib/libgs.9.53.dylib ct-logo.dvi

and get my svg.

So could there be some ownership issues while installing with the installer from your page?

Doris





------------------------------

Message: 13
Date: Fri, 23 Oct 2020 14:05:26 -0400
From: Ettore Aldrovandi <ealdrov at math.fsu.edu<mailto:ealdrov at math.fsu.edu>>
To: TeX on Mac OS X Mailing List <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <07E97364-CA71-40B6-82BA-95CDAE57B7B8 at math.fsu.edu<mailto:07E97364-CA71-40B6-82BA-95CDAE57B7B8 at math.fsu.edu>>
Content-Type: text/plain; charset="utf-8"


On Oct 23, 2020, at 13:53, Doris Behrendt via MacOSX-TeX <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>> wrote:

Hi Dick and others,

I?ll do that. But meanwhile I tried alternatives and wanted to let you know what I came up with and what problem occurred on the way:

install ghostscript via brew

(base) Doriss-Mac-mini:logo bd$ brew link --overwrite ghostscript
Linking /usr/local/Cellar/ghostscript/9.53.3...
Error: Could not symlink share/doc/ghostscript/9.53.3/API.htm
/usr/local/share/doc/ghostscript/9.53.3 is not writable.


So, following this link https://apple.stackexchange.com/questions/192227/how-to-make-files-in-usr-local-writable-for-homebrew

I had to temporarily change the ownership of the folder /urs/local

I changed from root:wheel to me:staff and after I did this, the linking went through:

brew link --overwrite ghostscript
Linking /usr/local/Cellar/ghostscript/9.53.3... 568 symlinks created

after this, I could finally run

dvisvgm --libgs=/usr/local/Cellar/ghostscript/9.53.3/lib/libgs.9.53.dylib ct-logo.dvi

and get my svg.

So could there be some ownership issues while installing with the installer from your page?

Doris,

glad you got it to work.

The ownership is most likely not an issue. When you install HomeBrew it prompts you to change ownership of /usr/local to yourself so that you don?t have to use ?sudo? all the time. The best time to do it is before you install anything else, otherwise you have to do a recursive ?chown -R?, as you have seen from the stackexchange link. By the way, it?s probably better to chown to yourself:wheel, instead of yourself:staff.

Also , brew symlinks into /usr/local, by default, so you would find your library in /usr/local/lib/libgs.9.53.dylib (shorter path).

?Ettore

Ettore Aldrovandi
Department of Mathematics, Florida State University
1017 Academic Way                *   http://www.math.fsu.edu/~ealdrov
Tallahassee, FL 32306-4510, USA * * aldrovandi at math dot fsu dot edu



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://email.esm.psu.edu/pipermail/macosx-tex/attachments/20201023/2989e239/attachment-0001.htm>

------------------------------

Message: 14
Date: Fri, 23 Oct 2020 11:42:31 -0700
From: "koch at uoregon.edu<mailto:koch at uoregon.edu>" <koch at uoregon.edu<mailto:koch at uoregon.edu>>
To: TeX on Mac OS X <macosx-tex at email.esm.psu.edu<mailto:macosx-tex at email.esm.psu.edu>>
Subject: Re: [OS X TeX] dvisvgm and ghostscript
Message-ID: <184A63C5-E4C2-4EF8-8622-D7AD9AF6D55B at uoregon.edu<mailto:184A63C5-E4C2-4EF8-8622-D7AD9AF6D55B at uoregon.edu>>
Content-Type: text/plain;              charset=us-ascii

Doris,

I'm happy you got things to work. Why not just accept the current situation and get on with your life? That's what I intend to do!

A note to others. The Ghostscript we install has been configured specially for TeX. These changes were made after research by Bruno Voisin and others. This is important in the Far East and unimportant for most of us. If you have special TeX needs, there may be a reason to use our install package.

A brief final note.

Apple creates /usr/local, and its permissions, as an empty folder when macOS is installed. This is necessary because even root does not have permission to add things to /usr in modern versions of macOS.

MacTeX is designed to just work with these Apple permissions, since most users do not want to manipulate file permissions.

Sometimes file permissions in /usr/local get changed, either deliberately as done by the brew system, or silently as done by a small number of software installers. Generally such changes make no difference, but diagnosing problems they cause is time consuming and I almost always leave that task to others or to the user.

Dick Koch


------------------------------

Subject: Digest Footer


-------------------------- Helpful Info --------------------------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://email.esm.psu.edu/mac-tex/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex
List Archive: http://tug.org/pipermail/macostex-archives/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/



------------------------------

End of MacOSX-TeX Digest, Vol 156, Issue 21
*******************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/macostex-archives/attachments/20201026/56989194/attachment-0001.html>
-------------- next part --------------
----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
                https://email.esm.psu.edu/pipermail/macosx-tex/
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex


More information about the macostex-archives mailing list.