Re: MacPorts missing links

Thanks very much for all your work on my issue: much appreciated. However, it’s looking like too much manual work, and also somewhat hazardous, at least to me as a non-expert. Moreover, I have no confidence that everything will be consistent, even if I successfully and correctly manually delete

Re: MacPorts missing links

On Sun, Sep 11, 2016 at 5:57 PM, David Epstein wrote: > and you have told me that “mp-llvm-3.5” is not the name of a port. I do > not understand the issues involved and their ramifications, so I may be > saying something stupid, but it seems to me, as a naive user,

Re: MacPorts missing links

> On Sep 11, 2016, at 5:37 PM, Lawrence Velázquez wrote: > >> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt wrote: >> >>> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt wrote: >>> On Sep 11, 2016, at 4:57 PM, David Epstein

Re: MacPorts missing links

> On Sep 11, 2016, at 6:24 AM, David Epstein > wrote: > > I hope that I’m believed when I say that I’m extremely careful never to > operate on /opt/local except via port. I do use programs like unix find and > unix ls that are not supposed to change anything. No,

Re: MacPorts missing links

On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote: > On my system I see the contents of that directory are provided by the > following ports: I think they're complaining that the directory itself should have been cleaned up. We don't have the concept of

Re: MacPorts missing links

> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt wrote: > > >> On Sep 11, 2016, at 4:57 PM, David Epstein >> wrote: >> >> Thanks very much for all your work on my issue: much appreciated. >> >> However, it’s looking like too much manual

Re: MacPorts missing links

> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt wrote: > >> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote: >>> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote: >>> >>> On my system I see the contents of that directory are provided by the >>> following ports: >>

Re: MacPorts missing links

> On Sep 11, 2016, at 5:57 PM, David Epstein > wrote: > > I’m not sure if I am allowed to put my name on some kind of cc list for the > ticket, since I’m not intending to work on the problem, but only want to know > when it has gone away. Feel free to Cc yourself

Re: MacPorts missing links

> On Sep 11, 2016, at 4:57 PM, David Epstein > wrote: > > Thanks very much for all your work on my issue: much appreciated. > > However, it’s looking like too much manual work, and also somewhat hazardous, > at least to me as a non-expert. Moreover, I have no

Re: MacPorts missing links

> On Sep 11, 2016, at 5:33 PM, Lawrence Velázquez wrote: > >> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt wrote: >> >>> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote: On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote: On my

Re: MacPorts missing links

> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt wrote: > >> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt wrote: >> >>> On Sep 11, 2016, at 4:57 PM, David Epstein >>> wrote: >>> >>> I do not understand the issues

Re: MacPorts missing links

On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote: > On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote: >> On my system I see the contents of that directory are provided by the >> following ports: > > I think they're complaining that the directory itself should have been > cleaned up. We

Re: MacPorts missing links

> On 11 Sep 2016, at 23:22, Ryan Schmidt wrote: > > On my system I see the contents of that directory are provided by the > following ports: > > $ port provides /opt/local/etc/select/python3/* > /opt/local/etc/select/python3/base is provided by: python3_select >

Re: MacPorts missing links

In view of all my moans and groans, I would like to make it clear that I think MacPorts is great, and it adds greatly to my productivity. I use it all the time, and tend to regard it as “Just there and working perfectly” usually without thinking of the arduous contributions being made behind

Re: MacPorts missing links

> On Sep 11, 2016, at 3:40 AM, David Epstein > wrote: > >> On 10 Sep 2016, at 23:10, Lawrence Velázquez wrote: > > … snip … > Did you uninstall python27? >>> >>> I think so. The ls -l command above does not find /opt/local/bin/python*,

Re: MacPorts missing links

On 11 Sep 2016, at 14:41, Lawrence Velázquez wrote: > >> On Sep 11, 2016, at 4:13 AM, David Epstein >> wrote: >> >> For those few interested in this thread, and who have not followed so far, >> the relevant line of output from >> “port select

Re: MacPorts missing links

livm was my error due to poor eyesight. It should have been llvm all the time. > On 11 Sep 2016, at 14:55, Sinan Karasu wrote: > > I don’t get the correspondence between “llvm” and “livm” in your posts. Is it > a typo, or are there really two different ports? > >> On Sep 11,

Re: MacPorts missing links

> On Sep 11, 2016, at 2:41 AM, David Epstein > wrote: > > I ran the suggested find command and double checked that all the entries are > broken symlinks. Ideally I would like to get rid of all of them, but safely. > From my point of view, the danger is that these

Re: MacPorts missing links

> On Sep 11, 2016, at 4:13 AM, David Epstein > wrote: > > For those few interested in this thread, and who have not followed so far, > the relevant line of output from > “port select —summary” was >> llvm none mp-llvm-3.5 none > > I think that this is a

Re: MacPorts missing links

I don’t get the correspondence between “llvm” and “livm” in your posts. Is it a typo, or are there really two different ports? > On Sep 11, 2016, at 1:13 AM, David Epstein > wrote: > >> livm ___ macports-users mailing

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

> On Sep 11, 2016, at 10:25 PM, Ken Cunningham > wrote: > > I would like to try building qemu, but it doesn't seem to be able to build > with clang-3.7 or clang-3.8 (on 10.68 with LibCxxOnOlderSystems and libc++) > > the error for both > :info:configure

qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

I would like to try building qemu, but it doesn't seem to be able to build with clang-3.7 or clang-3.8 (on 10.68 with LibCxxOnOlderSystems and libc++) the error for both :info:configure ERROR: Your compiler does not support the __thread specifier for :info:configureThread-Local

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

> On Sep 11, 2016, at 11:25 PM, Ken Cunningham > wrote: > > I am not totally sure how to use gcc* versions, building cxx code, when my > system has been set up for LibCxxOnOlderSystems, and all the installed ports > to date link against libc++. > > I _think_

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

> Someone else can elaborate if they want, but all I'll say at the moment is > that we have encountered an obscene amount of trouble involving g++, > libstdc++, and libc++, and a long time ago we basically decided that g++ was > dead to us. > > vq _That_ is exactly what has stopped me from

Re: MacPorts missing links

> On Sep 11, 2016, at 3:40 AM, David Epstein > wrote: > >> On 10 Sep 2016, at 23:10, Lawrence Velázquez wrote: > > … snip … > Did you uninstall python27? >>> >>> I think so. The ls -l command above does not find /opt/local/bin/python*,

Re: MacPorts missing links

I hope that I’m believed when I say that I’m extremely careful never to operate on /opt/local except via port. I do use programs like unix find and unix ls that are not supposed to change anything. Trying to demistify the line from the output of “port select —summary” > llvm none

Re: MacPorts missing links

> On 10 Sep 2016, at 23:13, Lawrence Velázquez wrote: > … snip … > Run this: > > find -L /opt/local -type l > > This will print any broken symlinks in your MacPorts prefix. Email the output > to this list, and we can tell you what you can safely delete. > > vq I

Re: MacPorts missing links

> On 10 Sep 2016, at 23:10, Lawrence Velázquez wrote: … snip … >>> Did you uninstall python27? >> >> I think so. The ls -l command above does not find /opt/local/bin/python*, >> except for symbolic links. >> What port command could I give to make sure? > > "port

Re: MacPorts missing links

> On 10 Sep 2016, at 23:05, Brandon Allbery wrote: …snip... > "port select --summary" reports as "none" in that case because the file > describing the previously selected option was removed and therefore is not a > valid setting. More to the point, if the options do not