Re: another 'wrong type argument' error

On Mon, 2022-10-17 at 20:11 +0100, Alex Harker wrote: > Thanks for clarifying what would be helpful. I’m currently trying to > get lilypond building locally with these scripts, although I’ve not > managed to fully complete that process yet. > > The dependencies were pretty much fine, but I had a

Re: another 'wrong type argument' error

Hi, I'm not a specialist of these topics, just replying to one specific point… Le 17/10/2022 à 21:11, Alex Harker a écrit : *In terms of Lilypond.app* - I suspect this would be useful to maintain - it’s how I was using it until my latest system (at which point I moved to Frescobaldi to have

Re: another 'wrong type argument' error

On 10/13/2022 11:30 PM, Werner LEMBERG wrote: actual Mac hardware I have a 2012 MacBook Air, Intel Core i5, 4 GB RAM, macOS Catalina 10.15.7, for an Apple-specific use case. I expect it will soon be left behind by the Apple upgrades train and need replaced for my purposes. I could donate

Re: another 'wrong type argument' error

Thanks for clarifying what would be helpful. I’m currently trying to get lilypond building locally with these scripts, although I’ve not managed to fully complete that process yet. The dependencies were pretty much fine, but I had a 404 with zlib whilst downloading the source and had to move

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

On Sun, 2022-10-16 at 11:20 +0200, Jacques Menu wrote: > > > > Le 15 oct. 2022 à 21:16, Jonas Hahnfeld a écrit > > : > > > > On Sat, 2022-10-15 at 21:09 +0200, Jacques Menu wrote: > > > Hello Jonas, > > > In my first attempt, I installed software on my machine with > > > Homebrew and MacPorts,

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

> Le 15 oct. 2022 à 21:16, Jonas Hahnfeld a écrit : > > On Sat, 2022-10-15 at 21:09 +0200, Jacques Menu wrote: >> Hello Jonas, >> >>> Le 14 oct. 2022 à 20:05, Jonas Hahnfeld a écrit : >>> >>> (regarding "automatically" in the title, please see my other reply) >>> >>> To be clear, I my self

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

On Sat, 2022-10-15 at 21:09 +0200, Jacques Menu wrote: > Hello Jonas, > > > Le 14 oct. 2022 à 20:05, Jonas Hahnfeld a écrit : > > > > (regarding "automatically" in the title, please see my other reply) > > > > To be clear, I my self am not working on this due to lack of hardware. > > If

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

Hello Jonas, > Le 14 oct. 2022 à 20:05, Jonas Hahnfeld a écrit : > > (regarding "automatically" in the title, please see my other reply) > > To be clear, I my self am not working on this due to lack of hardware. > If somebody wants to give it a try, that would again be great. I can of > course

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

(regarding "automatically" in the title, please see my other reply) On Fri, 2022-10-14 at 08:29 +0200, Jacques Menu wrote: > Hello folks, > > I’m a regular user of Mac OS, which I use for development, and > will help with the creation of LilyPond versions with pleasure. > > My last try at

Re: another 'wrong type argument' error

On Fri, 2022-10-14 at 04:30 +, Werner LEMBERG wrote: > > > > In the spirit of my first comments in this email I’ll directly ask > > if the project needs help testing or working on the Mac build > > system at all? > > Yes, we need help – namely for taking *permanent* care of the MacOS >

Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

Hello folks, I’m a regular user of Mac OS, which I use for development, and will help with the creation of LilyPond versions with pleasure. My last try at building LilyPond from the source code on my Mac Mini M1 failed due to a library not being ported yet to this architecture, but Jonas told

Re: another 'wrong type argument' error

>> So you checked all of LilyPond's dependencies and can guarantee >> that it will stay like this forever? > > I am on Big Sur (11.6) and I can still choose 10.9 as a deployment > target. [...] >> I'm not going to work on anything. I have been alone trying to get >> a build for macOS even

Re: another 'wrong type argument' error

David Wright writes: > No problem for a 1.5GHz 32-bit processor with 512MB memory. > BTW the term "plain x86" is almost meaningless. For a start, > are you talking about the processor, or the architecture? > Debian's "amd64" architecture is still an x86, just 64-bit. Well, for one thing one

Re: another 'wrong type argument' error

On Mon 10 Oct 2022 at 12:06:11 (+0100), Wols Lists wrote: > On 10/10/2022 06:43, Jean Abou Samra wrote: > > The problem isn’t LilyPond’s or its dependencies’ support for older macOS, > > which is better than even the system support. The real problem is Apple > > preventing you from upgrading

Re: another 'wrong type argument' error

On 10 Oct 2022, at 20:29, Jonas Hahnfeld wrote: > Yes, I build on macOS 10.15 and it will work on versions newer than > that, as also announced with the first release of this infrastructure: > https://lists.gnu.org/archive/html/lilypond-user/2022-02/msg00155.html I wanted to say that I didn’t

Re: another 'wrong type argument' error

Am Mi., 12. Okt. 2022 um 11:37 Uhr schrieb Thomas Morley : > > Am Mo., 10. Okt. 2022 um 21:04 Uhr schrieb Kieren MacMillan > : > > > > Hi Jean, > > > > > This looks like you have done something like > > > { c'\custdyn "p" } > > > instead of > > > { c'\custdyn "{p}" } > > > > Hmmm… the only three

Re: another 'wrong type argument' error

Am Mo., 10. Okt. 2022 um 21:04 Uhr schrieb Kieren MacMillan : > > Hi Jean, > > > This looks like you have done something like > > { c'\custdyn "p" } > > instead of > > { c'\custdyn "{p}" } > > Hmmm… the only three calls I have look like the second (correct) version, not > the first. But switching

Re: another 'wrong type argument' error

>> I read that SDK 10.14.1 supports 10.9 as the oldest version (I >> couldn't quickly find the lowest value for SDK 10.15).  AFAIK, we >> don't use any functionality that is available on newer macOS >> versions only, so this route seems safe. > > So you checked all of LilyPond's dependencies and

Re: another 'wrong type argument' error

On Mon, 2022-10-10 at 05:10 +, Werner LEMBERG wrote: > > Confirmed using otool that the minimum OS for the linked build is > > 10.15: > > > > Load command 10 > >    cmd LC_BUILD_VERSION > >    cmdsize 32 > >    platform 1 > >    minos 10.15 > >    sdk 10.15.6 > > Thanks. Yes, I

Re: another 'wrong type argument' error

On Mon, 2022-10-10 at 08:08 +0200, Jean Abou Samra wrote: > > > Le 9 oct. 2022 à 22:45, Kieren MacMillan a > > écrit : > > > > dyld: Symbol not found: _iconv > > Referenced from: /usr/lib/libcups.2.dylib > > Expected in: /opt/local/lib/libiconv.2.dylib > > in /usr/lib/libcups.2.dylib > >

Re: another 'wrong type argument' error

Hi Jean, > This looks like you have done something like > { c'\custdyn "p" } > instead of > { c'\custdyn "{p}" } Hmmm… the only three calls I have look like the second (correct) version, not the first. But switching those three custom dynamics to simple/native dynamics eliminates the error, so

Re: another 'wrong type argument' error

Le 10/10/2022 à 19:07, Kieren MacMillan a écrit : Hi Jean, Can you send the complete code? It seems to be missing the function dynamic-text::structered-list. I've attached the include file I use. Thanks! Kieren. This looks like you have done something like { c'\custdyn "p" } instead of

Re: another 'wrong type argument' error

Hi Jean, > Can you send the complete code? It seems to be missing > the function dynamic-text::structered-list. I've attached the include file I use. Thanks! Kieren. dynamics_on-the-fly.ly Description: Binary data

Re: another 'wrong type argument' error

Hi Jean, > Re screenshot: what editor are you using? > > In Frescobaldi, it seems that there is a glitch that prevents from > pasting from the log output if you have selected something at the same > time in the LilyPond code view, because that takes priority apparently, > but in my experience,

Re: another 'wrong type argument' error

p.s. > Looking at dynamics_on-the-fly.ly, line 294+ is > > (if (pair? prev-self-alignment-X-tweaks) > '() > (ly:grob-set-property! grob 'X-offset > (let* ((x-exts > (map >

Re: another 'wrong type argument' error

Le 10/10/2022 à 18:56, Kieren MacMillan a écrit : Hi Jean (et al.), Heh, 2.23.14 _just_ came out. MacPorts got updated. I upgraded. Good news! The maintainer is pretty reactive. try using that and putting #(ly:set-option 'compile-scheme-code) at the top of your file (before any

Re: another 'wrong type argument' error

Hi Jean (et al.), > Heh, 2.23.14 _just_ came out. MacPorts got updated. I upgraded. > try using that and putting #(ly:set-option 'compile-scheme-code) at the top > of your file (before any includes). > Also add #(debug-enable 'backtrace) for best results. Done. Result: Preprocessing

Re: another 'wrong type argument' error

Hi all, > one cannot expect bleeding-edge software to run on unsupported OSes For sure… I guess I just never thought of Lilypond as "bleeding-edge" before! :) > My point was to > temper the movement to investigate technical details of supporting > old macOS and remind that it is already

Re: another 'wrong type argument' error

Le 10/10/2022 à 13:06, Wols Lists a écrit : On 10/10/2022 06:43, Jean Abou Samra wrote: The problem isn’t LilyPond’s or its dependencies’ support for older macOS, which is better than even the system support. The real problem is Apple preventing you from upgrading your computer past a certain

Re: another 'wrong type argument' error

Wols Lists writes: > On 10/10/2022 06:43, Jean Abou Samra wrote: >> The problem isn’t LilyPond’s or its dependencies’ support for older >> macOS, which is better than even the system support. The real >> problem is Apple preventing you from upgrading your computer past a >> certain macOS

Re: another 'wrong type argument' error

On 10/10/2022 06:43, Jean Abou Samra wrote: The problem isn’t LilyPond’s or its dependencies’ support for older macOS, which is better than even the system support. The real problem is Apple preventing you from upgrading your computer past a certain macOS version. Which is probably down to

Re: another 'wrong type argument' error

>> That is certain to be the reason why it doesn’t run, but I suspect >> a local build might run fine. I’d suggest setting this lower for >> binary releases if there’s no pressing reason to require 10.15 on >> Mac. > > Sounds sensible. Jonas? And thanks for having done the release, Jonas!

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 22:45, Kieren MacMillan a > écrit : > > dyld: Symbol not found: _iconv > Referenced from: /usr/lib/libcups.2.dylib > Expected in: /opt/local/lib/libiconv.2.dylib > in /usr/lib/libcups.2.dylib > Abort trap: 6 What surprises me in this error message is that mentions a

Re: another 'wrong type argument' error

> Le 10 oct. 2022 à 07:10, Werner LEMBERG a écrit : > >> That is certain to be the reason why it doesn’t run, but I suspect a >> local build might run fine. I’d suggest setting this lower for >> binary releases if there’s no pressing reason to require 10.15 on >> Mac. > > Sounds sensible.

Re: another 'wrong type argument' error

> Confirmed using otool that the minimum OS for the linked build is > 10.15: > > Load command 10 > cmd LC_BUILD_VERSION > cmdsize 32 > platform 1 > minos 10.15 > sdk 10.15.6 Thanks. > That is certain to be the reason why it doesn’t run, but I suspect a > local build might run

Re: another 'wrong type argument' error

Hi Alex, > Confirmed using otool that the minimum OS for the linked build is 10.15: > > Load command 10 > cmd LC_BUILD_VERSION > cmdsize 32 > platform 1 > minos 10.15 > sdk 10.15.6 Oh! Fascinating. Thanks for digging that up. Kieren.

Re: another 'wrong type argument' error

Confirmed using otool that the minimum OS for the linked build is 10.15: Load command 10 cmd LC_BUILD_VERSION cmdsize 32 platform 1 minos 10.15 sdk 10.15.6 That is certain to be the reason why it doesn’t run, but I suspect a local build might run fine. I’d suggest setting this

Re: another 'wrong type argument' error

The computer under discussion (2011 Intel Core i7 iMac) has a 64 bit architecture and Mac OS 10.13 is 64 bit (Mac OS has had a 64 bit option since 10.6 and 10.8 removed the 32 bit kernel). This definitely isn’t likely to be a 64/32bit issue - I think that’s some kind of confusion. However,

Re: another 'wrong type argument' error

Jean Abou Samra writes: >> Le 9 oct. 2022 à 22:52, Kieren MacMillan >> a écrit : >> >> The moment I can afford a new computer for my studio, I'll upgrade! > > > Apart from buying new hardware, you could also run the Linux binaries > in a Linux VM. I would be surprised if a 64bit Linux would

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 22:52, Kieren MacMillan a > écrit : > > The moment I can afford a new computer for my studio, I'll upgrade! Apart from buying new hardware, you could also run the Linux binaries in a Linux VM. Jean

Re: another 'wrong type argument' error

Hi Jonas, > Probably not since all Intel Core processors should be 64-bit. It's > more likely that you are also running an ancient version of macOS. Oh, for sure: macOS 10.13.6 (the maximum this old iMac will run). > running an outdated and insecure operating system is bad by itself... The

Re: another 'wrong type argument' error

On Sun, 2022-10-09 at 16:24 -0400, Kieren MacMillan wrote: > Hi all, > > > Heh, 2.23.14 _just_ came out. > > https://gitlab.com/lilypond/lilypond/-/releases > > Kieren, try using that > > > When I download and unzip it, Frescobaldi doesn't like it: > > > I'm assuming it’s a 64-versus-32-bit

Re: another 'wrong type argument' error

Hi Jean, > If you type "~/Downloads/lilypond-2.23.14/bin/lilypond" in a terminal, > what does it give? dyld: Symbol not found: _iconv Referenced from: /usr/lib/libcups.2.dylib Expected in: /opt/local/lib/libiconv.2.dylib in /usr/lib/libcups.2.dylib Abort trap: 6 > Also, how did you install

Re: another 'wrong type argument' error

Le 09/10/2022 à 22:24, Kieren MacMillan a écrit : Hi all, Heh, 2.23.14 _just_ came out. https://gitlab.com/lilypond/lilypond/-/releases Kieren, try using that When I download and unzip it, Frescobaldi doesn't like it: [image] I'm assuming it’s a 64-versus-32-bit issue? (I'm working on a

Re: another 'wrong type argument' error

Hi Harm, > What happens if you follow the comments below? Cheers, Harm > >> ;; Next line should be used for 2.19.65 and above >> ;(ly:grob-set-property! grob 'stencil >> ; (stack-stencils X RIGHT 0 all-stils)) >> ;; This line is for

Re: another 'wrong type argument' error

Hi all, > Heh, 2.23.14 _just_ came out. > https://gitlab.com/lilypond/lilypond/-/releases > > Kieren, try using that When I download and unzip it, Frescobaldi doesn't like it: I'm assuming it’s a 64-versus-32-bit issue? (I'm working on a 2011

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 21:19, David Kastrup a écrit : > > Let's hope that better error > pinpointing starts working soonish. Heh, 2.23.14 _just_ came out. https://gitlab.com/lilypond/lilypond/-/releases Kieren, try using that and putting #(ly:set-option 'compile-scheme-code) at the top of

Re: another 'wrong type argument' error

> Le 9 oct. 2022 à 21:19, David Kastrup a écrit : > > No idea. Most can be ruled out, and for the other two one would have to > look at more context. > > It's really a clumsy way to debug. Not the least because the use of list-head could also be somewhere in Guile itself. For example,

Re: another 'wrong type argument' error

Kieren MacMillan writes: > Hi again, > > D'oh… The better implication for me to have gotten from your helpful > email would have been to search for "list-head" in all the files in my > path/folder… > > Here's the output of that effort: > > [from OLL] > edition-engraver/engine.scm:623: )

Re: another 'wrong type argument' error

Am So., 9. Okt. 2022 um 20:51 Uhr schrieb Kieren MacMillan : > > Hi David, > > > git grep list-head > > > > suggests woodwind diagrams, predefined fretboards, the function > > offset-fret, the \parallelMusic construct as possible callers. > > > > Anything in that list? > > I doubt it… > > > If

Re: another 'wrong type argument' error

Hi again, D'oh… The better implication for me to have gotten from your helpful email would have been to search for "list-head" in all the files in my path/folder… Here's the output of that effort: [from OLL] edition-engraver/engine.scm:623:) (wildcard2regex (list-tail

Re: another 'wrong type argument' error

Hi David, > git grep list-head > > suggests woodwind diagrams, predefined fretboards, the function > offset-fret, the \parallelMusic construct as possible callers. > > Anything in that list? I doubt it… > If not, my guess would be some edition-engraver > code when taking into account your

Re: another 'wrong type argument' error

Kieren MacMillan writes: > Anyone know where I should be looking to find the culprit? git grep list-head suggests woodwind diagrams, predefined fretboards, the function offset-fret, the \parallelMusic construct as possible callers. Anything in that list? If not, my guess would be some

Re: another 'wrong type argument' error

Hi Kieren, Le 09/10/2022 à 19:38, Kieren MacMillan a écrit : Hi again, Something still isn't working with a few of my scores, and I'm hoping someone can once again point me in the right direction for a quick fix… (No, a MWE isn't a real option.) — I'm running Lilypond 2.23.13 (installed

another 'wrong type argument' error

Hi again, Something still isn't working with a few of my scores, and I'm hoping someone can once again point me in the right direction for a quick fix… (No, a MWE isn't a real option.) — I'm running Lilypond 2.23.13 (installed via MacPorts) on macOS 10.13.6 (High Sierra) — I believe used