[MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.
MacPorts
noreply at macports.org
Tue Jun 23 11:30:14 PDT 2015
#47755: Broken symlink left by select code when selected port is deactivated causes
poppler and other ports using aclocal to fail during configuration.
-----------------------+--------------------------------
Reporter: lukasz@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.3.3
Resolution: | Keywords:
Port: |
-----------------------+--------------------------------
Comment (by m74z00219@…):
Replying to [comment:24 larryv@…]:
> Sorry, I forgot to update my comment. I replied on macports-users, not
macports-dev. I also addressed it to you directly, so you should have
received it already.
NP, though I still probably missed it. I subscribed to both macports-dev
and macports-users mailing lists, though haven't received a response. So,
I tried searching the archives, without luck.
Would you mind pointing me to your post?
Also, I would like to report that I can no longer launch wxmaxima
directly. It'll launch if I use "open /path/to/wxmaxima.app," though not
just by inputting "wxmaxima" as with other ports. Inputting "maxima" works
just fine. Why might this be? I figure it has something to do with the
removal of the above symlink and I know for a fact that
"/Applications/MacPorts/" was never part of my PATH variable. Even so, I
did try, in succession, adding "/Applications/MacPorts/" and
"/Applications/MacPorts/wxMaxima.app" to my PATH and still it would not
launch with "wxmaxima."
Here's some other stuff I tried. I "sudo port selfupdate" and "sudo port
upgrade outdated". I did it once more just to be sure. Unfortunately, the
problem persists.
Initially, I also had a problem with wxmaxima not being able to connect to
maxima. This was resolved by making sure that wxMaxima was listening to
the default port of xmaxima. Or, at least I think that's what did it.
Actually, I just played around with the port option and apparently it
still works, so...mystery. It connects so whatever.
I thought briefly about nuking my Macports installation, but that seems
like overkill as it seems that the problem is just with maxima. Honestly,
I'm so confused. There's also xmaxima -- where does that fit it in??
To sum up, what might explain the inability to launch wxmaxima from
command line?
Here's my PATH
{{{{
PATH=/opt/local/bin:/opt/local/sbin:/opt/local/etc/php56:/opt/local/apache2/bin:/opt/local/lib/mysql56/bin:~/bin:~/.composer/vendor/bin:${PATH}
}}}}
Thanks!
--
Ticket URL: <https://trac.macports.org/ticket/47755#comment:25>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list