Re: 10.6.8 and ffmpeg
libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk Ken On 2016-10-28, at 9:58 PM, Richard L. Hamilton wrote: > Am I right in thinking that ffmpeg now requires libsdl2 while it previously > required libsdl? That causes ffmpeg to fail on 10.6.x, because libsdl2 fails: > > Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 > requires OS X 10.7 SDK or later > Error: Failed to install libsdl2 > Please see the log file for port libsdl2 for details: > > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log > Error: The following dependencies were not installed: libsdl2 > Error: Unable to upgrade port: 1 > To report a bug, follow the instructions in the guide: >http://guide.macports.org/#project.tickets > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
10.6.8 and ffmpeg
Am I right in thinking that ffmpeg now requires libsdl2 while it previously required libsdl? That causes ffmpeg to fail on 10.6.x, because libsdl2 fails: Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 requires OS X 10.7 SDK or later Error: Failed to install libsdl2 Please see the log file for port libsdl2 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log Error: The following dependencies were not installed: libsdl2 Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error installing gnuplot/aquaterm
> On 29 Oct. 2016, at 3:00 am, macports-users-requ...@lists.macosforge.org > wrote: > >> I am sorry if this is a silly question, but I am trying to install gnuplot >> (I am running Mac OS Sierra, recently updated and performed the MacPorts >> migration) and am getting the error shown below. Aquaterm is needing to be >> installed and that seem to be where it is hanging up. >> >> Error: org.macports.activate for port aquaterm returned: Image error: >> /Applications/MacPorts/AquaTerm.app/Contents/Info.plist already exists and >> does not belong to a registered port. Unable to activate port aquaterm. Use >> 'port -f activate aquaterm' to force the activation. > > This looks like a local problem on your machines. Some files exist > that shouldn't be there. Try to run >sudo rm -rf /Applications/MacPorts/AquaTerm.app/ > and then try to install/activate aquaterm again. Alternatively do >sudo port -f activate aquaterm > as suggested. > > How did you uninstall MacPorts during migration? Just "sudo rm -rf > /opt/local"? Or did you actually do "sudo port deactivate active" or > "sudo port uninstall active"? If you just removed the contents of > "/opt/local" without uninstalling or deactivating old ports, you might > run into the same problem with other ports that install files outside > of $prefix. > > In that case I would suggest you to run "sudo port deactivate active", > then "rm -rf /Applications/MacPorts" and potentially clean up a few > more places (I have no clue which ones). You might have to force > install other ports if you didn't properly uninstall the ports from > earlier. First my gnuplot *does* run Next my install was messy and took many iterations I downloaded the install_sierra app and made a memstick I then updated and lots did not work (eg very important for me X11 forwarding) I then reinstalled el capitan only to find my time machine disk had beem marked as ‘sierra’ and could no longer be used. I did a fresh install (format disk) of sierra, then of macports, finally everything worked. I installed the ports I remembered, then as I found whoops needed, all was quick and the pain tolerable. James ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: command line tools for Xcode 8.1?
> On Oct 28, 2016, at 3:34 PM, Murray Eisenberg > wrote: > > Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. > > Release notes for Xcode 8.1 say: > > Known Issues > • There are no Command Line Tools (OS X 10.11) for Xcode 8.1. > Xcode 8.1 contains SDKs that are incompatible with earlier > toolchains. Developers who want to make use of the Xcode > 8 SDKs from the command line must choose the SDK with > xcode-select. Developers on OS X El Capitan who have installed > versions of the Command Line Tools (OS X 10.11) for Xcode 8.1 > should install Command Line Tools (OS X 10.11) for Xcode > 7.3.1. (28234439) > > How does that affect Macports? It doesn't. Nothing has changed since 8.0. https://lists.macosforge.org/pipermail/macports-dev/2016-September/033749.html vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: command line tools for Xcode 8.1?
On Fri, Oct 28, 2016 at 3:34 PM, Murray Eisenberg wrote: > Known Issues > >- There are no Command Line Tools (OS X 10.11) for Xcode 8.1. Xcode >8.1 contains SDKs that are incompatible with earlier toolchains. Developers >who want to make use of the Xcode 8 SDKs from the command line must choose >the SDK with xcode-select. Developers on OS X El Capitan who have >installed versions of the Command Line Tools (OS X 10.11) for Xcode 8.1 >should install Command Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439) > > How does that affect Macports? > Same way it did with 8.0. You should install the XCode 7.3.1 Command LIne Tools for 10.11 as specified. (So much for this being "fixed" in 8.1) -- 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
command line tools for Xcode 8.1?
Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. Release notes for Xcode 8.1 say: Known Issues There are no Command Line Tools (OS X 10.11) for Xcode 8.1. Xcode 8.1 contains SDKs that are incompatible with earlier toolchains. Developers who want to make use of the Xcode 8 SDKs from the command line must choose the SDK with xcode-select. Developers on OS X El Capitan who have installed versions of the Command Line Tools (OS X 10.11) for Xcode 8.1 should install Command Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439) <> How does that affect Macports? --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Home (240)-246-7240 Rockville, MD 20850-6667Mobile (413)-427-5334 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Moving to GitHub: Status Update, Action Required
On 10/28/16 7:18 AM, Rainer Müller wrote: > On 2016-10-28 16:02, Craig Treleaven wrote: >>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >>> ... >>> Migration Timeline >>> == >>> The switch to Git will happen on the weekend of October 29th/30th. ... >> >> Is this still on track? > > Yes, expect Subversion to go read-only this weekend. Shortly afterwards, > the repositories on GitHub will be the authoritative source for MacPorts. > > The infrastructure team did not schedule the exact time when this will > happen, but definitely this weekend. > Considering that this is a significant event, I'd appreciate it (and others might as well) if a specific date & time, expressed in UTC, could be published today for the disabling of subversion write access. Doesn't have to be a hard commitment for the infrastructure team. Even if it was something like "not earlier than ", it would help with planning. Thanks, Dave ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: zenmap issues
On Oct 28, 2016, at 9:43 AM, William Woods wrote: > >> On Oct 28, 2016, at 9:23 AM, Ryan Schmidt wrote: >> >> >>> On Oct 28, 2016, at 6:18 AM, William Woods wrote: >>> >>> So, I installed nap +zenmap, it installed fine, but: >>> >>> >>> >>> bash-4.4$ which zenmap >>> /opt/local/bin/zenmap >>> bash-4.4$ sudo zenmap >>> Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. >>> I checked in these directories: >>> /opt/local/bin >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages >>> >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0 >>> If you installed Zenmap in another directory, you may have to add the >>> modules directory to the PYTHONPATH environment variable. >>> bash-4.4$ >>> >>> any ideas ? >> >> See https://trac.macports.org/ticket/46429 >> > OK sure, but any idea of when will be fixed to work normally ? I know nothing more about this issue than what I just read in the ticket. I see there is a workaround shown there that you can use until the maintainer resolves the problem. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: zenmap issues
OK sure, but any idea of when will be fixed to work normally ? > On Oct 28, 2016, at 9:23 AM, Ryan Schmidt wrote: > > >> On Oct 28, 2016, at 6:18 AM, William Woods wrote: >> >> So, I installed nap +zenmap, it installed fine, but: >> >> >> >> bash-4.4$ which zenmap >> /opt/local/bin/zenmap >> bash-4.4$ sudo zenmap >> Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. >> I checked in these directories: >> /opt/local/bin >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages >> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0 >> If you installed Zenmap in another directory, you may have to add the >> modules directory to the PYTHONPATH environment variable. >> bash-4.4$ >> >> any ideas ? > > See https://trac.macports.org/ticket/46429 > > > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error installing gnuplot/aquaterm
On Oct 28, 2016, at 4:36 AM, Mojca Miklavec wrote: > In that case I would suggest you to run "sudo port deactivate active", > then "rm -rf /Applications/MacPorts" and potentially clean up a few > more places (I have no clue which ones). Fortunately, it's documented in the Guide: https://guide.macports.org/chunked/installing.macports.uninstalling.html -- Daniel J. Luke ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: zenmap issues
> On Oct 28, 2016, at 6:18 AM, William Woods wrote: > > So, I installed nap +zenmap, it installed fine, but: > > > > bash-4.4$ which zenmap > /opt/local/bin/zenmap > bash-4.4$ sudo zenmap > Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. > I checked in these directories: >/opt/local/bin > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip >/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0 > If you installed Zenmap in another directory, you may have to add the > modules directory to the PYTHONPATH environment variable. > bash-4.4$ > > any ideas ? See https://trac.macports.org/ticket/46429 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Moving to GitHub: Status Update, Action Required
On 2016-10-28 16:02, Craig Treleaven wrote: >> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >> ... >> Migration Timeline >> == >> The switch to Git will happen on the weekend of October 29th/30th. ... > > Is this still on track? Yes, expect Subversion to go read-only this weekend. Shortly afterwards, the repositories on GitHub will be the authoritative source for MacPorts. The infrastructure team did not schedule the exact time when this will happen, but definitely this weekend. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Moving to GitHub: Status Update, Action Required
> On Oct 28, 2016, at 9:02 AM, Craig Treleaven wrote: > >> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: >> ... >> Migration Timeline >> == >> The switch to Git will happen on the weekend of October 29th/30th. ... > > Is this still on track? Yes. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: trouble building mtr 0.87 on snow leopard. portfile patched?
> On Oct 28, 2016, at 5:03 AM, Peter Hancock wrote: > > On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. > The trouble, according to the log, is that IPPROTO_SCTP isn't defined. The > failing compile is: > > :info:build /usr/bin/gcc-4.2 -DHAVE_CONFIG_H -I. -I/opt/local/include > -pipe -Os -arch i386 -Wall -Wno-pointer-sign -MT net.o -MD -MP -MF > .deps/net.Tpo -c -o net.o net.c > > This is after several "sudo port clean mtr "s. > I'd no problems with upgrading mtr on a 2012 mini running yosemite. > > I looked at the trac.macports.org, and the last 154082 changeset gives some > diffs to the > portfile. Quite possibly I'm not looking at the right thing, but the patch > doesn't > seem to have been applied to the portfile used by the failing build. (There > were no > complaints about checksums in the build.) > > I'm reluctant to uninstall mtr and reinstall it, as 0.86 functions and is > very useful. > Anyone else have this issue? > > Otherwise I've done most(?) things one should do before creating a ticket. > Worth doing? Upstream already had a bug report and solution for this, so I applied it to the port: https://trac.macports.org/changeset/154358 Hopefully that resolves it. Since you already used a hack to install the port without that fix, you should probably rebuild it. Wait an hour or two for the fix to make it to our servers, then: sudo port selfupdate sudo port -n upgrade --force mtr ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Moving to GitHub: Status Update, Action Required
> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote: > ... > Migration Timeline > == > The switch to Git will happen on the weekend of October 29th/30th. ... Is this still on track? Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...
On 28/10/16 14:08, Peter Hancock wrote: On 28/10/2016 13:10, Chris Jones wrote: On 28/10/2016 11:03, Peter Hancock wrote: On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/include/netinet/in.h and give IPPROTO_SCTP the same value (132) as it has on the Yosemite machine on which mtr build. It built, and seems to work (for what I use it for, anyway). Needless to say, that is not a good idea, hacking the system files... Yes of course it's Wrong. (Once it built, I removed the hack.) Sadly I've never learnt how to use "patch" or indeed (m?)any of the tools one needs to tweak things in macports ... I don't really care what you do to your own machines, in private. Just don't post advice like this to the list, for others to follow ;) Please also keep your replies on-list. Chris Instead you should patch the source for mtr to define IPPROTO_SCTP in some appropriate header file there... Peter ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...
On 28/10/16 12:45, Peter Hancock wrote: On 28/10/2016 11:03, Peter Hancock wrote: On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/include/netinet/in.h and give IPPROTO_SCTP the same value (132) as it has on the Yosemite machine on which mtr build. It built, and seems to work (for what I use it for, anyway). Needless to say, that is not a good idea, hacking the system files... Instead you should patch the source for mtr to define IPPROTO_SCTP in some appropriate header file there... Chris ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: trouble building mtr 0.87 on snow leopard. Solved with a hack...
On 28/10/2016 11:03, Peter Hancock wrote: > On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. > The trouble, according to the log, is that IPPROTO_SCTP isn't defined. What I did was to edit /usr/include/netinet/in.h and give IPPROTO_SCTP the same value (132) as it has on the Yosemite machine on which mtr build. It built, and seems to work (for what I use it for, anyway). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
zenmap issues
So, I installed nap +zenmap, it installed fine, but: bash-4.4$ which zenmap /opt/local/bin/zenmap bash-4.4$ sudo zenmap Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'. I checked in these directories: /opt/local/bin /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0 If you installed Zenmap in another directory, you may have to add the modules directory to the PYTHONPATH environment variable. bash-4.4$ any ideas ? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
trouble building mtr 0.87 on snow leopard. portfile patched?
On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87. The trouble, according to the log, is that IPPROTO_SCTP isn't defined. The failing compile is: :info:build /usr/bin/gcc-4.2 -DHAVE_CONFIG_H -I. -I/opt/local/include -pipe -Os -arch i386 -Wall -Wno-pointer-sign -MT net.o -MD -MP -MF .deps/net.Tpo -c -o net.o net.c This is after several "sudo port clean mtr "s. I'd no problems with upgrading mtr on a 2012 mini running yosemite. I looked at the trac.macports.org, and the last 154082 changeset gives some diffs to the portfile. Quite possibly I'm not looking at the right thing, but the patch doesn't seem to have been applied to the portfile used by the failing build. (There were no complaints about checksums in the build.) I'm reluctant to uninstall mtr and reinstall it, as 0.86 functions and is very useful. Anyone else have this issue? Otherwise I've done most(?) things one should do before creating a ticket. Worth doing? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error installing gnuplot/aquaterm
On 28 October 2016 at 06:23, Tom Gederberg wrote: > I am sorry if this is a silly question, but I am trying to install gnuplot > (I am running Mac OS Sierra, recently updated and performed the MacPorts > migration) and am getting the error shown below. Aquaterm is needing to be > installed and that seem to be where it is hanging up. > > Error: org.macports.activate for port aquaterm returned: Image error: > /Applications/MacPorts/AquaTerm.app/Contents/Info.plist already exists and > does not belong to a registered port. Unable to activate port aquaterm. Use > 'port -f activate aquaterm' to force the activation. This looks like a local problem on your machines. Some files exist that shouldn't be there. Try to run sudo rm -rf /Applications/MacPorts/AquaTerm.app/ and then try to install/activate aquaterm again. Alternatively do sudo port -f activate aquaterm as suggested. How did you uninstall MacPorts during migration? Just "sudo rm -rf /opt/local"? Or did you actually do "sudo port deactivate active" or "sudo port uninstall active"? If you just removed the contents of "/opt/local" without uninstalling or deactivating old ports, you might run into the same problem with other ports that install files outside of $prefix. In that case I would suggest you to run "sudo port deactivate active", then "rm -rf /Applications/MacPorts" and potentially clean up a few more places (I have no clue which ones). You might have to force install other ports if you didn't properly uninstall the ports from earlier. Mojca ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
