<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">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:</div><div class=""><br class=""></div><div class=""><font face="Osaka-Mono" class=""><span style="font-style: normal;" class="">albemuth:~/tmp> ls -l /opt/brw/Cellar/ghostscript/9.53.3/lib <br class="">total 26584<br class="">-r--r--r-- 1 ealdrov wheel 13610904 Oct 2 07:59 libgs.9.53.dylib<br class="">lrwxr-xr-x 1 ealdrov wheel 16 Oct 2 07:59 libgs.9.dylib@ -> libgs.9.53.dylib<br class="">lrwxr-xr-x 1 ealdrov wheel 16 Oct 2 07:59 libgs.dylib@ -> libgs.9.53.dylib</span></font><br class=""><br class=""></div><div class=""><br class=""></div><div class="">—Ettore</div></div></div></blockquote><br class=""></div><div>Folks,</div><div><br class=""></div><div>When Ghostscript is compiled from source, the usual </div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>./configure</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>make</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>sudo make install</div><div><br class=""></div><div>sequence does not create or install the ghostscript library. The library is created with a special command</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>make so</div><div><br class=""></div><div>and three files are then placed in the folder sobin inside the source directory. Two are symbolic links,</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.dylib</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.dylib.9</div><div><br class=""></div><div>and one is an actual library,</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.dylib.9.53</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>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 </div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>sudo make install</div><div><br class=""></div><div>places the gs binary and many other scripts in /usr/local/bin, but installs everything else in</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>/usr/local/share/ghostscript/9.53.3</div><div><br class=""></div><div>and this folder even contains a subfolder named lib. So that seemed to be a natural place to put the actual dynamic library.</div><div><br class=""></div><div>As for symbolic links, I decided to break my own rule and add three links to /usr/local/lib named</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.dylib</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.9.dylib</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>libgs.9.53.dylib</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>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.)</div><div><br class=""></div><div> 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.</div><div><br class=""></div><div>Dick Koch</div></body></html>