Pinfo will not build with Clang from Xcode 4.4

[greeneg (Gary Greene)]

On Mountain Lion and Xcode 4.4 (4F250)'s version of clang, pinfo will not build. If you add the following snippet to the Portfile, it will however:

if {${configure.compiler} == "clang"} {
    configure.compiler llvm-gcc-4.2
}

Attached is my updated version of the Portfile. Thanks.

[greeneg (Gary Greene)]

Updated version of pinfo's Portfile to use LLVM compiler

[ryandesign (Ryan Carsten Schmidt)]

Simpler: just add this line:

compiler.blacklist clang

Instead of a complete new Portfile, you should provide a unified diff of your changes so that they are easier to review. I'll attach this.

When you report that a port will not build, you should attach the main.log file so that we can see how it failed. I'll attach this too. The error it shows is:

:info:build Undefined symbols for architecture x86_64:
:info:build   "_buildcommand", referenced from:
:info:build       _openinfo in pinfo-filehandling_functions.o
:info:build   "_builddircommand", referenced from:
:info:build       _opendirfile in pinfo-filehandling_functions.o
:info:build ld: symbol(s) not found for architecture x86_64

[ryandesign (Ryan Carsten Schmidt)]

It was stated in comment:ticket:35549:1 that the port built fine with clang on Lion. Not knowing whether this was because of a difference in the OS or in the Xcode version, I assumed the latter, and as part of r96281 I blacklisted clang only with Xcode 4.4 and up.

However, the Lion buildbot (which last I heard was using Xcode 4.3.2) ​failed to build pinfo, with the same error message as above. I then tried building with macports-clang-3.0 on my Mountain Lion machine, and it also failed as above. So in the absence of an actual main.log showing a successful build with some version of clang, I went back to blacklisting clang always, as I had originally planned, in r96297.

[master@…]

OK, it is not worth investigating why it built for me on Lion and failed in other cases. I'll recheck the case when I get a clean updated environment on a new Mountain Lion Mac.

[ryandesign (Ryan Carsten Schmidt)]

Is it possible you were using Xcode 4.0 or 4.1? On those versions of Xcode, MacPorts would default to using llvm-gcc-4.2, not clang.

[jmroot (Joshua Root)]

Did you try clang with -std=gnu89?

[ryandesign (Ryan Carsten Schmidt)]

Thanks, that seems to work. r96305