Alright I was hopeful I had solved the problem, but it appears not. Here's what I did. I replaced the system iconv with gnu-libiconv, so that when I did "iconv -l" I can see MAC ROMAN as an option. I did a new clean build of fontforge. When it was configuring I saw lines saying that it was going to use my system iconv instead of the light version they use if it's not on the system already. That seemed good because I just replaced the system iconv with a better one. Then I did a clean configure and rebuild of lilypond. But alas, at the same point I got the same message and it hanged.
Are there any other thoughts on how to get past this? On Sat, Aug 24, 2024, 10:40 AM Werner LEMBERG <w...@gnu.org> wrote: > > >> > Your version of iconv does not support the "Mac Roman" > >> > encoding. If this causes problems, reconfigure --without-iconv. > >> > >> This error message is not part of LilyPond; we only access iconv > >> via the ice-9 module 'iconv' from Guile. > > > > So would I have to figure out how to compile that module with the > > --without-iconv option? Or is this just not going to work? > > I have to correct myself. This message comes from FontForge (you can > find your original error message string as being part of its git > repository). Note, however, that recent versions of FontForge no > longer have such a configuration option because it no longer uses > `autoconf` but `cmake` as a build tool. [The FontForge project is > comatose and barely alive, unfortunately.] > > Having a quick look it seems that you can use `libiconv` (instead of > using the OS version of `iconv`) for building FontForge, but I have > never tried that since it is not necessary on my GNU/Linux box. > > > Werner >
