On 10 Sep 2014, at 22:46 , Jeremy Huddleston Sequoia
wrote:
> ld64 supports a variant to use llvm-3.6 for LTO by default, so you may prefer
> to set that.
Yeah, I saw that and switched to that one.
> Yes, llvm-3.5 hasn't been bumped to the final release, but it is pulling from
> svn a few d
On 10 Sep 2014, at 22:34 , Lawrence Velázquez wrote:
> LLVM 3.5 was released a few days ago (although Jeremy hasn't bumped the port
> to the release version yet), while 3.6 is still very much in development.
Oh, I see…
Good to know, thanks.
___
macpor
ld64 supports a variant to use llvm-3.6 for LTO by default, so you may prefer
to set that.
Yes, llvm-3.5 hasn't been bumped to the final release, but it is pulling from
svn a few days before the release, so there isn't really much different between
it and final. I'll bump it soon because I kno
On Sep 10, 2014, at 4:22 PM, Marko Käning wrote:
> I noticed that installing clang-3.6 requires also installation of llvm-3.5
> because dependency ld64 selects it as the default variant.
ld64 and cctools use LLVM for libLTO and llvm-mc.
> Confusing, but there might be a reason for that...
>
>
I noticed that installing clang-3.6 requires also installation of llvm-3.5
because dependency ld64 selects it as the default variant.
Confusing, but there might be a reason for that...
Well, is it recommended to rather use version 3.5 ATM?
___
macports-
