Re: llvm-3.5 on 10.7.5
Thanks for the explanation, folks! As far as I can get, pre-10.9 / XCode pre-5 is not longer available for download. Probably port info should state a requirement of osx 10.9 or at least the error message itself, or provide a link the the FAQ :) Error: llvm-3.5 requires a C++11 runtime, which your configuration does not allow Just the message makes me ask what a configuration does it refer? Then one needs to open a port file and look for the message and then ask here :) Do I understand correctly, that it is possible to build the llvm/clang 3.5. But it requires proper libstdc++. What else does the C++11 ecosystem include? And the built code will require the C++11 ecosystem. Probably, static builds are a solution, aren't they? -- Regards, Alex ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
llvm-3.5 on 10.7.5
Hi, I have working llvm-3.5 @3.5-r198565_0+assertions. Recently, it was updated to @3.5-r202097. An attempt to upgrade results in a message: Error: llvm-3.5 requires a C++11 runtime, which your configuration does not allow The cause is presence of /usr/lib/libc++.dylib as far as I can get. Does it mean that llvm-3.5 does not work on 10.7? -- Regards Alex ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: llvm-3.5 on 10.7.5
On Wed, Feb 26, 2014 at 4:49 PM, Alexey Luchko soulne...@gmail.com wrote: I have working llvm-3.5 @3.5-r198565_0+assertions. Recently, it was updated to @3.5-r202097. An attempt to upgrade results in a message: Error: llvm-3.5 requires a C++11 runtime, which your configuration does not allow The cause is presence of /usr/lib/libc++.dylib as far as I can get. Does it mean that llvm-3.5 does not work on 10.7? By itself, it works fine. The problem is that it is never by itself; it exists in an ecosystem whose contents are defined by Apple. On 10.7 that ecosystem is not C++11, and while you can build a C++11 ecosystem of your own it is not compatible with anything else. In particular it is not compatible with any C++ libraries provided by Apple as part of the base system or Xcode, and if you ever try to use an Apple-compatible C++ library with it you will get link errors or possibly crashes. After playing whack-a-mole for a while trying to get stuff to coexist, MacPorts has given up and acknowledged that the only thing that works reliably is to go with what is compatible with Apple libraries; that means only older llvm that uses pre-C++11 interfaces (provided by libstdc++ or an Apple-sourced compatible libc++) on pre-10.9 and only newer llvm that uses C++11 interfaces (provided by modern libc++ but not the libc++ shipped on older OS X) on 10.9. Any other combination *might* work if you are lucky but is not guaranteed in any way, and MacPorts no longer supports it. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: llvm-3.5 on 10.7.5
On Feb 26, 2014, at 16:12, Brandon Allbery wrote: Does it mean that llvm-3.5 does not work on 10.7? By itself, it works fine. The problem is that it is never by itself; it exists in an ecosystem whose contents are defined by Apple. On 10.7 that ecosystem is not C++11, and while you can build a C++11 ecosystem of your own it is not compatible with anything else. In particular it is not compatible with any C++ libraries provided by Apple as part of the base system or Xcode, and if you ever try to use an Apple-compatible C++ library with it you will get link errors or possibly crashes. After playing whack-a-mole for a while trying to get stuff to coexist, MacPorts has given up and acknowledged that the only thing that works reliably is to go with what is compatible with Apple libraries; that means only older llvm that uses pre-C++11 interfaces (provided by libstdc++ or an Apple-sourced compatible libc++) on pre-10.9 and only newer llvm that uses C++11 interfaces (provided by modern libc++ but not the libc++ shipped on older OS X) on 10.9. Any other combination *might* work if you are lucky but is not guaranteed in any way, and MacPorts no longer supports it. Them’s some good words there, Bradley. Do you feel up to turning it into a FAQ entry? It’s a complicated thing to explain to people and it would be great if there were a central explanation we could refer people to. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: llvm-3.5 on 10.7.5
On Wed, Feb 26, 2014 at 6:32 PM, Ryan Schmidt ryandes...@macports.orgwrote: Them’s some good words there, Bradley. Do you feel up to turning it into a FAQ entry? It’s a complicated thing to explain to people and it would be great if there were a central explanation we could refer people to. Will http://trac.macports.org/wiki/FAQ#libcpp do? -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: llvm-3.5 on 10.7.5
On Feb 26, 2014, at 18:51, Brandon Allbery allber...@gmail.com wrote: On Wed, Feb 26, 2014 at 6:32 PM, Ryan Schmidt ryandes...@macports.org wrote: Them’s some good words there, Bradley. Do you feel up to turning it into a FAQ entry? It’s a complicated thing to explain to people and it would be great if there were a central explanation we could refer people to. Will http://trac.macports.org/wiki/FAQ#libcpp do? Great, thanks! ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
