old_contents: GitHubTarballPackage('mono', 'libgdiplus', '2.11', '4e7ab0f555a13a6b2f954c714c4ee5213954ff79', configure = 'CFLAGS="%{gcc_flags} %{local_gcc_flags} -I/opt/X11/include" ./autogen.sh --prefix="%{package_prefix}"')
  
new_contents: GitHubTarballPackage('mono', 'libgdiplus', '2.11', '4e7ab0f555a13a6b2f954c714c4ee5213954ff79', configure = 'CFLAGS="%{gcc_flags} %{local_gcc_flags} -I/opt/X11/include" ./autogen.sh --prefix="%{package_prefix}"', override_properties = { 'make': 'C_INCLUDE_PATH="" make' })
  
subject: Fix incorrect building of libgdiplus on Mavericks bots. Fixes #23553. There is an #include file resolution problem when C_INCLUDE_PATH is set to the install prefix (as bockbuild does), leading to a build where CAIRO_HAS_QUARTZ_SURFACE is not defined, so GdipCreateFromContext_macosx() wasn't built. I couldn't decipher what exactly changes in the includes when the prefix path loses precedence (when C_INCLUDE_PATH is unset so it's only in CFLAGS), and the Xcode toolchain selected didn't seem to matter, but indeed unsetting C_INCLUDE_PATH results in fixing the build. So this will have to do for now.