cairo @1.10.2_4+no_x11 fails building when /usr/bin/gcc-4.2 is present with Xcode 4.2

[jerkejacobs@…]

Dear all,

I tried installing doxygen +no_x11 and it got stuck on the cairo dependency.

[jerkejacobs@…]

Build log

[raimue (Rainer Müller)]

Looks similar to #32087.

[ryandesign (Ryan Carsten Schmidt)]

What version of Xcode do you have? #32087 was about users who had Xcode >= 4.2, yet somehow also had /usr/bin/gcc-4.2.

[raimue (Rainer Müller)]

When upgrading from Xcode <4.2 the App Store installer does not remove old files. Thus, /usr/bin/gcc-4.2 will exist for many users. We cannot tell which older version of Xcode was installed before the update. The Xcode installer from the App Store does not populate the receipt database (which would have been useful for stuff like pkg-util --file-info). This file might as well be from an ancient version such as Xcode 3.x -- imagine a user just upgrading from Snow Leopard.

The reason to disable both llvm-gcc-4.2 and clang in cairo was #31469, where build problems were encountered. I was able to build cairo using clang (although port test fails, but so does it with gcc-4.2). Building with llvm-gcc-4.2 would probably work when removing -flto from the LDFLAGS with a patch for the configure script or in post-configure with a reinplace for the Makefile.

$ xcodebuild -version
Xcode 4.2.1
Build version 4D502

[raimue (Rainer Müller)]

Cc Me!

[raimue (Rainer Müller)]

Here is a patch to the cairo port adding an additional patch for the configure script to disable lto when building using llvm-gcc-4.2.

(Sorry, I realize I somehow high-jacked this ticket. But I believe the problem reported here is caused by using an ancient /usr/bin/gcc-4.2.)

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #32087.

[robin@…]

Cc Me!