On Wed, Jan 31, 2024 at 12:49 AM Werner LEMBERG <w...@gnu.org> wrote:
> > > 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? > All errors happened during 'make doc'. They appeared to happen after all of the lilypond processing was done, while creating the html documentation pages. I've attached three compressed log files. One shows the cp error (when I was using MacOS cp command by default). The second shows the find error (after configuring my system to use GNU cp). The third shows the perl error (after configuring my system to use GNU find as well as GNU cp). This link shows an example of what might cause the cp error (as well as the homebrew way to avoid it): https://github.com/sahib/rmlint/issues/275 This link shows how to get the GNU find utilities on MacOS, but doesn't reference the particular error in the log file. It does, however, indicate that there are a number of differences between the MacOS find and the GNU find.: https://unix.stackexchange.com/questions/277914/find-not-working This link shows how the -name argument can lead to the observed error message: https://unix.stackexchange.com/questions/369771/find-command-not-working-illegal-option-n > 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`. > That's the recommendation I found on the web, but I don't know the Makefile well enough to propose a patch using xargs. Thanks for all your work on this! Carl
cp_error.make.doc.log.gz
Description: GNU Zip compressed data
find_error.make.doc.log.gz
Description: GNU Zip compressed data
perl_error.make.doc.log.gz
Description: GNU Zip compressed data
