t;. If the clang
> project decides to match Apple and call the next version 4.0 instead of 3.2
> then we'll have to rename the clang-3.2 port and the "configure.compiler
> macports-clang-3.2" option.
clang versioning is all kinds of problematic and confusing. This is not
On 2012-8-17 08:42 , Mojca Miklavec wrote:
> Hello,
>
> I would like to ask if there are any approximate time plans to make
> macports-clang-3.2 compiler part of officially released MacPorts. The
> reason why I'm asking is because TextMate2's build procedure requires
> As a side question If 3.2 is not released, how does it then related to the
> Xcode version of clang with OSX 10.8, which appears to report itself as
> version 4.0 ? Or is this just Apple doing its own thing again... Or have I
> mis read the versions...
Forget that ... Dumb question. Answered
On Aug 16, 2012, at 18:37, Chris Jones wrote:
> On 16 Aug 2012, at 11:51 PM, Ryan Schmidt wrote:
>
>> On Aug 16, 2012, at 17:42, Mojca Miklavec wrote:
>>
>>> I would like to ask if there are any approximate time plans to make
>>> macports-clang-3.2 compiler
Hi,
On 16 Aug 2012, at 11:51 PM, Ryan Schmidt wrote:
>
> On Aug 16, 2012, at 17:42, Mojca Miklavec wrote:
>
>> I would like to ask if there are any approximate time plans to make
>> macports-clang-3.2 compiler part of officially released MacPorts. The
>> reaso
On Aug 16, 2012, at 17:42, Mojca Miklavec wrote:
> I would like to ask if there are any approximate time plans to make
> macports-clang-3.2 compiler part of officially released MacPorts. The
> reason why I'm asking is because TextMate2's build procedure requires
>
Hello,
I would like to ask if there are any approximate time plans to make
macports-clang-3.2 compiler part of officially released MacPorts. The
reason why I'm asking is because TextMate2's build procedure requires
it if XCode 4.4 is not installed. I fixed the problem locally, but
ot
