Re: another 'wrong type argument' error

[Alex Harker]

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, is it possible that the build process for the newest lilypond release 
discussed sets a minimum Mac OS of higher than 10.13? Mac OS settings for this 
compiler variable are hard limits, even if the code could compile/run on a 
lower OS. Something about 10.13 would seem a little conservative for an 
open-source project of this nature.

I had a super-quick skim of the source, and beyond seeing that it looks like a 
GNU make build system, I could only see that it was likely too complex for me 
to be able to easily figure out what would be happening here quickly. If 
nothing is being set for a minimum OS then it will (I believe) default to the 
OS it is being compiled on - that might be the source of the issue.

Alex


> On 9 Oct 2022, at 23:16, David Kastrup <dak@gnu.org> wrote:
> 
> Jean Abou Samra <jean@abou-samra.fr> writes:
> 
>>> Le 9 oct. 2022 à 22:52, Kieren MacMillan
>>> <kieren@kierenmacmillan.info> 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 be supported by a VM on a
> 32bit OS.
> 
> -- 
> David Kastrup
>