LLVM not supported on Sierra?

Ken Cunningham ken.cunningham.webuse at gmail.com
Mon Oct 3 06:44:00 CEST 2016


llvm-3.5 is not supported on macOS Sierra or newer.

I don't think llvm-3.5 is a version to be used. One of the Apple engineers
frequently steers people to newer versions.

Why not llvm-3.7, 3.8, or 3.9?

On Sun, Oct 2, 2016 at 8:05 PM, Dave Horsfall <dave at horsfall.org> wrote:

> Doing a "port upgraded outdated" after installing Sierra (and had some
> trouble with X11), I get this:
>
> --->  Computing dependencies for llvm-3.5
> --->  Fetching distfiles for llvm-3.5
> Error: llvm-3.5 is not supported on macOS Sierra or newer.
> Error: org.macports.fetch for port llvm-3.5 returned: unsupported platform
> Please see the log file for port llvm-3.5 for details:
>
> /opt/local/var/macports/logs/_opt_local_var_macports_
> sources_rsync.macports.org_release_ports_lang_llvm-3.5/llvm-3.5/main.log
> Error: Unable to upgrade port: 1
>
> main.log:
>
> version:1
> :msg:main --->  Computing dependencies for llvm-3.5:info:main .:debug:main
> Searching for dependency: xz
> :debug:main Found Dependency: receipt exists for xz
> :msg:main
> :debug:main Executing org.macports.main (llvm-3.5)
> :debug:main changing euid/egid - current euid: 0 - current egid: 20
> :debug:main egid changed to: 20
> :debug:main euid changed to: 502
> :debug:fetch fetch phase started at Mon Oct  3 13:55:43 AEDT 2016
> :notice:fetch --->  Fetching distfiles for llvm-3.5
> :debug:fetch Executing proc-pre-org.macports.fetch-fetch-0
> :debug:fetch Executing proc-pre-org.macports.fetch-fetch-1
> :error:fetch llvm-3.5 is not supported on macOS Sierra or newer.
> :error:fetch org.macports.fetch for port llvm-3.5 returned: unsupported
> platform
> :debug:fetch Error code: NONE
> :debug:fetch Backtrace: unsupported platform
>     while executing
>     "proc-pre-org.macports.fetch-fetch-1 org.macports.fetch"
>     ("eval" body line 1)
>         invoked from within
> "eval $pre $targetname"
> :info:fetch Warning: targets not executed for llvm-3.5:
> org.macports.destroot or
> rg.macports.configure org.macports.build
> :notice:fetch Please see the log file for port llvm-3.5 for details:
>     /opt/local/var/macports/logs/_opt_local_var_macports_
> sources_rsync.macports.org_release_ports_lang_llvm-3.5/llvm-3.5/main.log
>
> Is this a problem with Macports itself?  Or have I screwed up as usual?
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20161002/0c7fc02d/attachment.html>


More information about the macports-users mailing list