lilypond-devel @2.19.83_2: error: expected initializer before '__OSX_AVAILABLE_STARTING'

[dliessi (Davide Liessi)]

A user reported this build error ​here, attaching the main.log file ​here (I attach that file to this ticket). I'll take care of keeping the user informed of the development of this ticket.

This does not seem a duplicate of #58913.

MacOS 10.14.6 Xcode 11.0

[kencu (Ken)]

This would seem to be another example of the fact that gcc cannot build things against the new MacOSX10.15.sdk headers in Xcode 11, because at present gcc does not handle these macros:

__OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_5, __MAC_10_6, __IPHONE_NA, __IPHONE_NA);

<​https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835>

[nerdling (Jeremy Lavergne)]

kencu: any updates? Tempted to close and just point at #59113.

[kencu (Ken)]

I think they fixed gcc -- Iain certainly had fixes in. did they not?

Otherwise I can come up with some very simple defines for you like this to disappear them:

#define __OSX_AVAILABLE_BUT_DEPRECATED(...)

[kencu (Ken)]

didn't do anything special port -v install lilypond-devel

looks like it built with clang now.

checking for gcc... /usr/bin/clang

$ port -v installed | grep lilypond
  lilypond-devel @2.21.2_0 (active) platform='darwin 18' archs='x86_64' date='2020-06-30T22:47:20-0700'

[nerdling (Jeremy Lavergne)]

Sounds like things are now working without modifying lilypond ourselves.