Re: Error with texi2pdf on MacOS
> 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). OK. This was a very specific problem with your setup and does not happen in the normal case, I think. Werner
Re: Error with make doc
> I already had to install (via homebrew) gnu coreutils and gnu > findutils, since the MacOS 'cp' and 'find' commands don't work the > same as the respective GNU commands. Please give more details. What problems did you experience with `cp` and `find`? Did this happen during a call to `make ...` for LilyPond? This should work out of the box, which essentially means that we have to either add tests to `configure` to catch the problematic tools, or to rewrite the commands in the makefile or scripts to avoid issues with GNU-style usage of those tools, for example. > I then get to a problem with perl: [...] Interesting. I wasn't aware that we ever call `perl` with a long list of arguments during `make doc`. Please repeat this with saying ``` make doc VERBOSE=1 &> make.doc.log ``` so that we can more information in the log file. Usually, such errors can easily be circumvented by using `xargs`. Werner
Re: Error with make doc
Still trying to get 'make doc' to complete successfully. At this point, I think I'm through all the lilypond stuff, and now I'm stuck in shell script errors. I already had to install (via homebrew) gnu coreutils and gnu findutils, since the MacOS 'cp' and 'find' commands don't work the same as the respective GNU commands. I then get to a problem with perl: carl@carls-mbp-2 build % make doc Making out-www/offline-root/index.html Processing HTML pages for offline target... /bin/sh: /opt/local/bin/perl: Argument list too long make[1]: *** [out-www/offline-root/index.html] Error 126 make[1]: *** Deleting file `out-www/offline-root/index.html' make: *** [doc] Error 2 The internet suggests I should look at getconf ARG_MAX: build % getconf ARG_MAX 1048576 This seems like it should not be a problem. Any suggestions for debugging this? Thanks, Carl
Re: Error with texi2pdf on MacOS
On Sat, Jan 27, 2024 at 12:45 AM Werner LEMBERG 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/` 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!
