If the port still fails to install after you have followed these steps, please file a ticket and attach the main. The installation of a single port consists of multiple phases. These phases are fetch, extract, patch, configure, build, destroot, archive, and finally install. You may break up a port's installation into smaller steps for troubleshooting by using the name of one of these phases as action rather than install.
For example. By default, a binary sanity check called rev-upgrade is run automatically after each successful installation. Pass this flag, if you want to avoid running this step, for example if you want to run it explicitly later after a number of installations using sudo port rev-upgrade , or if you know it will detect problems but want to defer dealing with them. If you want MacPorts to treat a port you installed manually as if it was automatically installed as a dependency e.
The action clean deletes intermediate files created by MacPorts while installing a port.
A port clean is often necessary when builds fail and should be the first thing to try after a failed installation attempt. Remove the work directory, i.
This removes all traces of an attempted build and is the default operation. The uninstall action will remove an installed port. It is one of the actions you will use fairly often in MacPorts. You can recursively uninstall all ports that depend on the given port before uninstalling the port itself to work around this. To do that, use the --follow-dependents flag. You can also override this safety check using the -f force flag.
Since this will obviously break the dependents you shouldn't do this unless you know what you are doing. Uninstalling a port will not uninstall ports that have been automatically installed as dependencies of the uninstalled port and are otherwise unused. You can trigger this behavior by passing the --follow-dependencies flag. Ports that were manually installed i. You can manually uninstall the unneeded ports later using the leaves pseudo-port, e.
Recursively uninstall ports that depend on the specified port before uninstalling the port itself. See also the textual description above. Also uninstall ports that were automatically installed as dependencies of the removed port and are no longer needed. The contents action displays a list of all files that have been installed by a given port.
You can only use contents for ports you installed. Common uses for contents are finding the location of a port's executable after installing it. The following line is usually helpful in this case:. The -q quiet flag suppresses the header line in this case, but is not strictly necessary. Used in conjunction with --size to choose the unit of the file size. Valid parameters for UNIT are.
Worked for me too. Copy link Quote reply. You might be the type who likes to compile packages your self, then this info is not useful. Gnuplot appears to be working now…. Post by Jaime Villate Hi Michel, in this second case you are no longer using gnuplot. Sorry, your blog cannot share posts by email. Leave your comments here: Name E-mail.
The installed action displays the installed versions and variants of the specified ports, or if no ports are specified, all installed ports. Use -v to also display the platform and CPU architecture s for which the ports were built, and any variants which were explicitly negated. The outdated action checks your installed ports against the current ports tree to see they have been updated since you installed them. Note that you will only get new versions by updating your ports tree using selfupdate or sync. In most cases, this will be an increase in the version number.
If it isn't, more details will be given. The upgrade action upgrades installed ports and their dependencies to the latest version available in MacPorts.
In most cases, you will run. You can, however, selectively upgrade ports if you want to delay other upgrades until later.
This is not recommended unless you know what you are doing, since you might experience software errors for the ports that have not yet been upgraded. To upgrade individual ports, specify the name s of the port s to upgrade:.
Note that MacPorts may decide to upgrade other dependent ports before upgrading the port you requested to be updated. Do not attempt to prevent this, since it will very likely lead to problems later. Instead, it deactivates it, i. This allows you to go back to the older version if there happens to be a problem with the updated one.
To do that, run. If you do not want to keep the old versions around while upgrading, you can pass -u when upgrading:. If the installed variants do not match those requested, upgrade and change variants even if the port is not outdated.
You can use this to switch the variant selection on an installed port, e. Note that --enforce-variants will also enforce your variant selection in all dependencies. If you know this is not necessary, you can avoid processing dependencies using the global -n flag:. Do not automatically install replacement ports for a port that you have installed, but was replaced with a different one.
The dependents action reports what ports depend upon a given installed port, if any. Note that dependents does not work for ports that are not installed on your system. If you want to find out, which ports depend on a port that you have not installed, you can use. This command will, however, not cover dependencies that are only present in non-default variants.
The livecheck action checks to see if the application corresponding to a given port has been updated at the developer's download site. This action is mostly useful for port maintainers to determine whether their port needs to be updated, but other may also wish to see if a port packages the latest available version. If livecheck finds no higher version at the port's download site, it prints nothing. The option -d debug may be used for detailed livecheck processing information.
The lint action checks if the Portfile conforms to the MacPorts standards specified in Portfile Development. You should use this if you modified a Portfile before submitting patches back to MacPorts.
Variants are a way for port authors to provide options for a port that may be chosen at installation. Typically, variants are optional features that can be enabled, but are not necessarily useful for all users and are thus not enabled by default. To display the available variants for a port, if any, use this command:.
If a variant depends on or conflicts with other variants, a line with the details on that follows. A variant can only be selected when a port is installed. After you have determined what variants a given port has, if any, you may install a port using a variant by specifying its name preceded by a plus sign on the command line, for example. Note that you will not see any confirmation of successful variant selection and MacPorts will not warn you if you misspelled a variant's name. If your installation is successful, but the chosen feature still seems to be missing, check for possible typos.
You can use port installed to verify that the port has been installed with the chosen variant. This happens because MacPorts will also use the specified variants for any dependencies. MacPorts will remember the variants that were used when installing a port.
If you upgrade a port later, the same variants will be used, unless you manually specify different variants. A Portfile can specify a default set of variants that will be used when you do not manually override it. Not all ports specify default variants — if there are no default variants, no variants are chosen by default. If you wish to disable a variant that has been enabled by default, either by the Portfile , or by your configuration in variants.
This section lists common operations you may want to perform when managing a MacPorts installation. These are the workflows you will need most while using MacPorts. We recommend you read at least this section as a primer into how to use MacPorts. The local ports tree is a collection of files that contain information on which packages are available through MacPorts and how they can be installed. You should regularly update your ports tree to get access to updated versions of software and bug fixes. To do that, use selfupdate :. To see what's new after running selfupdate , you can use port outdated to generate a list of ports that have newer versions available.
This can help in estimating the time required for sudo port upgrade outdated , even though this depends on further factors such as binary package availability and a port's build time. Note that MacPorts will upgrade any dependencies of a port first before updating the port itself. So even if you request the update of a single port only, other ports may be upgraded first because they are in the dependency tree.
Do not try to avoid this, as it will very likely lead to problems later on — the new version of the port you want to upgrade might require the newer dependency, or it might only have been upgraded at all to be rebuilt against the updated dependency, in which case avoiding the update of the dependency defeats the purpose of the reinstallation.
By default, upgrading ports in MacPorts does not remove the older versions.
App name: AquaTerm; App description: aquaterm (App: rengentguardsigpo.tk); App website: brew cask install aquaterm iMac, Macbook, OSX, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard, Tiger. Re: [AQT-user] interfering gnuplot aquaterm and sourceforge installation od AT. From: Mojca .. [AQT-user] aqua term in gnuplot stalled since getting osx Lion.
This is a safety measure to ensure you can go back to a working and tested version in case an update goes wrong.