On Sat, Jan 27, 2024 at 12:45 AM Werner LEMBERG <w...@gnu.org> wrote:
> > Ouch. You have two TeX installations in your path: MacTeX (either > installed directly or via homebrew) and 'texlive-xxx' packages from > MacPorts, and the former is apparently missing XeTeX support (for > whatever reason) since the `xdvipdfmx` binary is missing. You have to > decide which one to use. Given that you are mostly relying on > MacPorts it's probably simpler to use MacPorts binaries. > > If you don't want delete the non-MacPorts TeX installation you should > separate it. The simplest solution is probably to remove the symbolic > link `/Library/TeX/texbin` completely (the actual MacTeX tree is > `/usr/local/texlive/<year>` for homebrew, too) or to remove > `/Library/TeX/texbin` from your PATH environment variable. This makes > your MacPort's 'texlive' package the default. > You are correct that I had MacTex installed directly (and used with TeXShop) and texlive-xxx from MacPorts. The problem was actually not that MacTeX did not support XeTeX, but that the MacPorts texlive-xxx did not included texlive-xetex (so there was no xetex in my texlive path; the xetex that was found was the MacTex xetex). The solution was to install texlive-xetex in MacPorts. Once that was done, 'make doc' completed successfully. Thank you SO MUCH for helping me work through these issues. It's nice to be able to build lilypond natively on my Mac. Now I can get to work trying to get Charles Winston's work on chord semantics integrated into the code base. At any rate, your help with getting my environment up and running has been invaluable. Carl > Note that the attached archive is broken (and it doesn't use any > compression). What about simply using `gzip` to compress single files > in the future? Alternatives are `xz`, `bzip2`, or similar programs. > P.S. This was a mistake due to my reversing the order of the arguments to 'tar'. I overwrote the log file with an empty archive, and then created an archive of overwritten log file, rather than of the original log file. Probably much easier to use any single file compression program. Thanks for the suggestion!
