Re: MacPorts missing links

> On 12 Sep 2016, at 17:39, Lawrence Velázquez wrote: >> I should read more documentation on “port select”. I think that “man port” >> does not give an adequate explanation, and I would welcome a pointer to >> fuller documentation about “port select”. > > The new

Re: MacPorts missing links

> On Sep 13, 2016, at 3:06 AM, David Epstein > wrote: > > One thing that seems to be brought out (by the erroneous answer by “port > provides ligpng.la") It's not erroneous, in the sense that libpng.la really does exist and belong to the libpng port. The problem,

Re: MacPorts missing links

> On Sep 13, 2016, at 2:06 AM, David Epstein > wrote: > > >> On 13 Sep 2016, at 03:19, Ryan Schmidt wrote: >> >> >>> On Sep 12, 2016, at 9:08 PM, Brandon Allbery wrote: >>> >>> On Mon, Sep 12, 2016 at 9:59 PM,

Re: MacPorts missing links

On Tue, Sep 13, 2016 at 3:06 AM, David Epstein wrote: > One thing that seems to be brought out (by the erroneous answer by “port > provides ligpng.la > > ") is that I made a mistake when updating the OS, to have updated my > MacPorts installation, > Um, a bunch of

Re: MacPorts missing links

> On 13 Sep 2016, at 03:19, Ryan Schmidt wrote: > > >> On Sep 12, 2016, at 9:08 PM, Brandon Allbery wrote: >> >> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt >> wrote: >> What do you get when you run: >> port provides

Re: MacPorts missing links

On Sep 12, 2016, at 8:23 PM, Lawrence Velázquez wrote: >> I would also encourage somebody to look into the need for both Xcode and >> Command Line Tools since Xcode 7. Apple makes it quite clear on the download >> page that Xcode now contains the CLTs, so installing both

Re: MacPorts missing links

I get the same thing. I have only 3 or 4 ports. So I’ll blow it away and start from scratch tomorrow to see what happens. pirlouit:~ sinan$ port provides /opt/local/lib/libpng.la /opt/local/lib/libpng.la is provided by: libpng pirlouit:~ sinan$ > On Sep 12, 2016, at 7:19 PM, Ryan Schmidt

Re: MacPorts missing links

On Mon, Sep 12, 2016 at 11:02 PM, Al Varnell wrote: > In all the years I've been using MacPorts I have never needed to reinstall > the MacPorts base for a minor upgrade. I think that's stated, although maybe not clearly enough. Needing to do that on a minor upgrade would be

Re: MacPorts missing links

On Mon, Sep 12, 2016 at 10:24 PM, Dave Horsfall wrote: > Hmmm... I've been following this thread, and I get: > > /opt/local/lib/libpng.la > And... just checked my 10.11 as well. Indeed: skkukkuk «crawl*master» Z$ sudo find -L /opt/local -type l > >

Re: MacPorts missing links

On Mon, 12 Sep 2016, Ryan Schmidt wrote: > > pirlouit:~ sinan$ sudo find -L /opt/local -type l > > /opt/local/lib/libpng.la > > pirlouit:~ sinan$ > > > > The one you say I shouldn’t get. And that is the only one. Hmmm... I've been following this thread, and I get: /opt/local/lib/libpng.la

Re: MacPorts missing links

> On Sep 12, 2016, at 9:08 PM, Brandon Allbery wrote: > > On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt wrote: > What do you get when you run: > port provides /opt/local/lib/libpng.la > > They actually provided that earlier: > > >

Re: MacPorts missing links

On Sep 12, 2016, at 6:25 AM, David Epstein wrote: > When I now run >> sudo find -L /opt/local -type l -exec port provides {} + > > I get >> /opt/local/lib/libpng.la is provided by: libpng >> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac >>

Re: MacPorts missing links

> On Sep 12, 2016, at 10:53 AM, Sinan Karasu wrote: > > >> On Sep 12, 2016, at 4:25 AM, David Epstein >> wrote: >> >>> sudo find -L /opt/local -type l >>> For example, libpng.la should not have existed on your system, if your OS >>> is

Re: MacPorts missing links

> On Sep 12, 2016, at 7:25 AM, David Epstein > wrote: > > When I now run >> sudo find -L /opt/local -type l -exec port provides {} + > > I get >> /opt/local/lib/libpng.la is provided by: libpng >> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac >>

Re: MacPorts missing links

> On Sep 11, 2016, at 7:59 PM, David Epstein > wrote: > > 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

Re: MacPorts missing links

> On Sep 12, 2016, at 4:25 AM, David Epstein > wrote: > >> sudo find -L /opt/local -type l >> For example, libpng.la should not have existed on your >> system, if your OS is Mavericks or later. Now you made me curious. My OS is Sierra, and has

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 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

> 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: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: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 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 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: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 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 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 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

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 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 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

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: 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 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

> 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 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: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

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: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 Sep 10, 2016, at 5:51 PM, David Epstein > wrote: > > I do not want to rely on my memory of which of these I have uninstalled. I > need to be told by a reliable program. Run this: find -L /opt/local -type l This will print any broken symlinks in your

Re: MacPorts missing links

> On Sep 10, 2016, at 5:51 PM, David Epstein > wrote: > >> On 10 Sep 2016, at 19:38, Lawrence Velázquez wrote: >> >> Did you uninstall python27? > > I think so. The ls -l command above does not find /opt/local/bin/python*, > except for

Re: MacPorts missing links

On Sat, Sep 10, 2016 at 5:51 PM, David Epstein wrote: > What would happen if I gave one of your commands below, with argument a > port that was still installed? "port select --summary" reports as "none" in that case because the file describing the previously

Re: MacPorts missing links

Thanks for your help: > On 10 Sep 2016, at 19:38, Lawrence Velázquez wrote: > >> On Sep 10, 2016, at 1:42 PM, David Epstein >> wrote: >> >> I gave the command: >> >> ls -l /opt/local/bin/py* >> and the system replied: >> >>> lrwxr-xr-x 1

Re: MacPorts missing links

On 10 September 2016 at 20:38, Lawrence Velázquez wrote: > >> I wonder what causes this kind of problem? I cannot remember any of my port >> processes terminating incorrectly. I have lately been uninstalling >> python-related ports, because I had too many different versions of python on >> my

Re: MacPorts missing links

> On Sep 10, 2016, at 1:42 PM, David Epstein > wrote: > > I gave the command: > > ls -l /opt/local/bin/py* > and the system replied: > >> lrwxr-xr-x 1 root wheel 23 9 Jun 19:13 /opt/local/bin/pydoc@ -> >> /opt/local/bin/pydoc2.7 >> lrwxr-xr-x 1 root wheel

MacPorts missing links

I gave the command: ls -l /opt/local/bin/py* and the system replied: > lrwxr-xr-x 1 root wheel 23 9 Jun 19:13 /opt/local/bin/pydoc@ -> > /opt/local/bin/pydoc2.7 > lrwxr-xr-x 1 root wheel 23 9 Jun 17:19 /opt/local/bin/pydoc3@ -> > /opt/local/bin/pydoc3.5 > lrwxr-xr-x 1 root wheel 24