[117006] trunk/dports/lang/gccxml-devel/Portfile

[Ryan Schmidt]

On Feb 15, 2014, at 13:47, Rainer Müller <raimue at macports.org> wrote:

> On 2014-02-12 20:24, Ryan Schmidt wrote:
>> 
>> On Feb 12, 2014, at 12:13, mmoll at macports.org wrote:
>> 
>>> Revision
>>> 117006
>>> Author
>>> mmoll at macports.org
>>> Date
>>> 2014-02-12 10:13:18 -0800 (Wed, 12 Feb 2014)
>>> Log Message
>>> 
>>> lang/gccxml-devel: after some more testing it turns out that neither gcc* nor clang* work, so just use llvm-gcc-4.2. Add llvm-gcc-4.2 as a runtime dependency since it gets invoked by gccxml.
>>> Modified Paths
>>> 
>>> 	• trunk/dports/lang/gccxml-devel/Portfile
>> 
>>> +configure.compiler llvm-gcc-4.2
>> 
>> To my surprise, this works, even on Xcode 5. "configure.compiler llvm-gcc-4.2” means llvm-gcc42 provided by Xcode, but Xcode 5 and later doesn’t provide llvm-gcc42. The configure output on the buildbot and on my system shows that as long as llvm-gcc42 is installed, it finds the MacPorts version of llvm-gcc42 instead; I guess find_developer_tool also looks in ${prefix}.
> 
> We do not look in ${prefix} specifically. It's actually xcrun/xcodebuild
> that also seems looks in PATH for the tool,
> from my OS X 10.9 Mavericks with Xcode 5:
> 
>  $ xcrun -find llvm-gcc-4.2
>  /opt/local/bin/llvm-gcc-4.2
>  $ xcodebuild -find llvm-gcc-4.2
>  /opt/local/bin/llvm-gcc-4.2
> 
> I am also wondering if this is actually the intended behavior or just a
> coincidence?

From my point of view, it’s unintended. If we fix this bug, and make “configure.compiler llvm-gcc-4.2” refer only to Xcode-provided llvm-gcc-4.2 as was originally intended, then the port will need to be changed, perhaps to “compiler.whitelist llvm-gcc-4.2 macports-llvm-gcc-4.2”.