| Version 116 (modified by neverpanic (Clemens Lang), 10 years ago) (diff) |
|---|
Problem Hotlist
Table of Contents
-
Problem Hotlist
- MacPorts stops working after installing Xcode 4.3 or later
- Error message from "port upgrade outdated": uninstall failure: "an invalid entry was passed"
- A port build fails on Snow Leopard with: "file is not of required architecture"
- A port fails to build when using Xcode 4/5
- install_name_tool or strip reports "malformed object (unknown load command)"
- Incompatible library version: X requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
- man port fails with error message
- port fails with: Image error: /opt/local/bin/a2p…
- Fetch failures
- Image error: /opt/local/bin/xmlwf already exists and does not belong to a registered port
- A port failed to build with a message referring to 1/lib: No such file or directory
- Corrupt Filemap
- Retired Problems
MacPorts stops working after installing Xcode 4.3 or later
Support for Xcode 4.3 was added in MacPorts 2.0.4. If you have an earlier version of MacPorts, you will need to upgrade to be able to use Xcode 4.3.
xcode-select
There have been reports of xcode-select not pointing to the new Xcode location for some users after upgrading from an Xcode version older than 4.3. If you are having problems even with the latest MacPorts version and xcode-select -print-path does not print /Applications/Xcode.app/Contents/Developer on your system, or
Warning: Xcode appears to be installed but xcodebuild is unusable; some ports will likely fail to build.
then you need to run:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
This is particularly important for people who have error messages referring to their old compiler locations after installing Xcode later than 4.2: you need to reinstall the package that stored the old compiler location if you see an error message like this:
error: can't exec '/Developer/usr/bin/<compiler>' (No such file or directory)
So far this error is seen in previously-built perl and python when building perl or python modules. For example, if a py27-xxxx port fails to install and the log contains error messages of this type, try reinstalling the main python27 port with:
sudo port -n upgrade --force python27
Note you might have an older version of the xcode-select tool in case you installed Xcode 4.2 after installing the Mac OS X 10.7.3 update. If the command xcode-select -version returns version 2003, this is from Xcode 4.2 and we recommend to install the update once again with the Mac OS X 10.7.3 combo updater. The current xcode-select version that comes with Mac OS X 10.7.3 identifies itself as version 2307.
Xcode License Agreement
When attempting to build a port which compiles an OS X app (e.g., gimp-app), the compilation may fail with an xcodebuild error. One of the possible causes of this is that an initial run of xcodebuild from the terminal may be needed to accept the EULA before any compilation can proceed. Run:
xcodebuild -license
from a terminal window and follow the prompts. After accepting the EULA, rebuild the port again.
With some ports and some versions of Xcode (e.g. libunwind-headers with Xcode 4.4+) you may need to accept the license as root, i.e.:
sudo xcodebuild -license
This will need to be repeated after any Xcode upgrade.
Error message from "port upgrade outdated": uninstall failure: "an invalid entry was passed"
Before MacPorts 2.1.3 it was possible to leave the registry in an inconsistent state if an uninstallation was interrupted. Although this has been fixed in version 2.1.3, the fix does not cure a previously corrupt registry.
The perl script attached to the ticket about this bug fixes the registry. The direct link is here.
A port build fails on Snow Leopard with: "file is not of required architecture"
If you had MacPorts installed before upgrading to Snow Leopard, see Migration.
A port fails to build when using Xcode 4/5
gcc has been the compiler collection MacPorts has used by default up until Xcode 4, in which Apple has switched to the llvm/clang compiler collection. These are new compilers and many programs have not yet been tested with them, and some ports will fail as a result. Using a different compiler may work better for a particular port. If the below workarounds enable you to install a port that failed with its default compiler, file a ticket and let us know so we can fix it. Portfile authors, see wiki:PortfileRecipes#compiler.
Xcode 4.2 and later (including Xcode 5)
If a port foo fails to build and you're using Xcode 4.2 or later, the default compiler is clang; try compiling with llvm-gcc-4.2 instead:
sudo port clean foo sudo port install foo configure.compiler=llvm-gcc-4.2
If that fails, try installing the apple-gcc42 port and compiling with that:
sudo port clean foo sudo port install apple-gcc42 sudo port install foo configure.compiler=apple-gcc-4.2
Xcode 4.0 and 4.1
If a port foo fails to build and you're using Xcode 4.0 or 4.1, the default compiler is llvm-gcc-4.2; try compiling with clang instead:
sudo port clean foo sudo port install foo configure.compiler=clang
If that fails, try using gcc-4.2:
sudo port clean foo sudo port install foo configure.compiler=gcc-4.2
install_name_tool or strip reports "malformed object (unknown load command)"
An error message like:
install_name_tool: object: libfoo.dylib malformed object (unknown load command 8)
or:
strip: object: libbar.dylib malformed object (unknown load command 9)
indicates that your install_name_tool or strip commands (both are part of the Xcode command line tools) are too old to deal with the types of objects produced by the compiler. (The number after "unknown load command" may be different.) This can happen if you have forgotten to update the Xcode command line tools to a version designed for your version of OS X.
Incompatible library version: X requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
You might see this error when running a program, or in the main.log or config.log when a port fails to configure or build:
dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib Referenced from: /path/to/X Reason: Incompatible library version: X requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
This usually means libiconv is installed for the wrong architecture(s) and needs to be rebuilt. To rebuild libiconv:
sudo port -n upgrade --force libiconv
But if libiconv's architecture was wrong, it's likely other ports have the similar problem. The usual reason for architecture mismatches is that you migrated from Leopard or earlier to Snow Leopard or later and did not follow the migration instructions. Another possible culprit is installing a third-party software package that was itself created using MacPorts, which overwrote some of your MacPorts files; see #xmlwf for more on this.
The error message is confusing. What OS X should be saying is: "The program or library X is linked with /opt/local/lib/libiconv.2.dylib and requires version 8.0.0 of that library. /opt/local/lib/libiconv.2.dylib is at least version 8.0.0, but it's built for the wrong architecture, so I'm going to look around for another libiconv.2.dylib. Ok, I found /usr/lib/libiconv.2.dylib and it's built for the right architectures, so I'll use that instead. Wait, /usr/lib/libiconv.2.dylib is only version 7.0.0. That's too old for X. I'll display an error message that the version is too old."
Another possible culprit is that you have DYLD_LIBRARY_PATH set in your environment; if so, try unsetting it.
man port fails with error message
Error message:
$ man port Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>") No manual entry for port
Workaround:
Add the following line to your .profile or .bash_profile.
unset MANPATH
Ticket: #13444
port fails with: Image error: /opt/local/bin/a2p…
Error message:
Error: Activating perl5 @5.12.3_1 failed: Image error: /opt/local/bin/a2p is being used by the active perl5.8 port. Please deactivate this port first, or use the -f flag to force the activation.
The perl5.8, perl5.10 and perl5.12 ports used to conflict with each other unless a particular variant was selected. This has now been solved by suffixing their binaries with a version number, and the perl5 port installs links without any suffix. The old versions of perl5.x conflict with the current version of perl5.
Fix:
To fix this issue, upgrade whichever of the above ports that you have installed.
port upgrade installed and \( perl5.8 perl5.10 perl5.12 \)
Fetch failures
If fetch failed for a port, you can still get the distfile from anywhere else. For example, the main MacPorts distfiles mirror contains most ports' distfiles, or maybe the homepage of the software lists alternative download locations for source tarballs. Just download the distfile and save it to the path shown by port distfiles <portname>. Make sure you get a file with exactly the same name (watch out for .tar.gz and .tar.bz2!) If a port clean --all has been done the distfile directory will have been removed. The directory for each port is created at the beginning of the fetch phase. After placing the distfile, run port install <portname>again.
Note: Checksum failures after a fetch are typically a separate issue. See the FAQ.
Image error: /opt/local/bin/xmlwf already exists and does not belong to a registered port
When installing a port with MacPorts, you encounter this error:
Error: Target org.macports.activate returned: Image error: /opt/local/bin/xmlwf already exists and does not belong to a registered port. Unable to activate port expat.
xmlwf is a part of the expat port (which is a dependency of many other ports, and thus is likely to be one of the first ports to ever get installed), but for some reason this file already exists on your computer, and MacPorts did not install it.
One possible reason for this is that you have installed a 3rd-party software package—possibly gprolog or swi-prolog or SMBup—which was itself built with MacPorts, set to its default prefix, and therefore conflicts with your normal use of MacPorts in its default prefix. The developers of the 3rd-party package you installed should not have distributed their software in this manner; they should have configured MacPorts in a custom prefix instead, one that is unique to their software. (For example, in the case of swi-prolog, /usr/local/swi-prolog or /opt/swi-prolog would be good choices.)
Another possible reason is that you previously had MacPorts (and expat and probably other ports) installed, then somehow uninstalled MacPorts itself, or at least its registry of which ports are installed, without actually uninstalling those ports, and have now installed MacPorts again with a clean registry, which therefore thinks no ports are installed, though some still are.
Either way, the cleanest solution at this point is to follow the MacPorts uninstallation instructions. This will remove the 3rd-party software package that installed itself unannounced into MacPorts' prefix, and/or ports installed by your prior MacPorts installation. Then you can install MacPorts again.
A port failed to build with a message referring to 1/lib: No such file or directory
Error message:
apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory make: *** Error 1
Explanation:
When upgrading from Tiger to Leopard without removing the previous Mac OS version, updated versions of some libraries in /usr/ and /usr/lib/ are moved from /old/path/ to /old/path 1/. Notice the space before 1. This makes some configure scripts build bad build instructions, making the build phases of several ports fail.
Two incriminated directories have been encountered :
/usr/X11R6 1/ /usr/lib/ruby 1/
Workaround:
In order to fix this problem, you can remove the backups created by the installers, and then clean the work directory of the failed port so that its configure script will be re-run:
port clean --work <port>
Corrupt Filemap
Error message:
Error: unknown node kind in database (database is corrupted?)
Workaround:
Probably something went wrong while a port was being (un)installed or (de)activated, such as a kernel panic or the machine losing power. You can fix the database file (/opt/local/var/macports/receipts/file_map.db) by downloading the following script:
http://svn.macports.org/repository/macports/contrib/repairfilemap/repairfilemap.tcl
Follow the instructions in the comments at the beginning of the script. You can invoke the script by typing:
chmod +x repairfilemap.tcl sudo ./repairfilemap.tcl
Retired Problems
The following problems are now solved, no longer apply to current MacPorts or should no longer be happening due to other circumstances. They are kept here for future reference and to avoid breaking existing links.
MacPorts port installs fail after an OS X upgrade
An installation of MacPorts and the ports installed by it are only designed to work on a single OS release and a single CPU architecture. So in most cases, MacPorts needs to be reinstalled after an OS upgrade.
See Migration, for OS X Mavericks problems see MavericksProblems.
Note: Starting with MacPorts 2.3.0, MacPorts will print an error message if this occurs and direct you to Migration. The message will read:
Current platform "darwin YZ" does not match expected platform "darwin XY" If you upgraded your OS, please follow the migration instructions: https://trac.macporst.org/wiki/Migration
Can't find Tcl configuration definitions
When installing MacPorts from source on 10.9, you may encounter the error
checking for Tcl configuration... configure: error: Can't find Tcl configuration definitions
The file tclConfig.sh was included in the Mac OS X base in earlier releases, but was moved to the Xcode Command Line Tools in 10.9; these are normally installed the first time you run clang after accepting the Xcode license, but running the configure script doesn't run clang until after the Tcl check. The easiest way to force installation is to run:
xcode-select --install
after installing Xcode 5.0.1 or later.
Note: This can no longer occur starting with MacPorts 2.3.0, because it ships its own copy of Tcl.
MacPorts port installs fail on OS X Lion 10.7 after a fresh App Store installation of Xcode
The port command will remind you to install Xcode (or upgrade if you have an old version lying around from a previous installation of OS X). This is most easily accomplished using the "App Store" application on your Mac, which requires an Apple ID. Xcode 4.5 is the version currently available for Lion from the App Store.
However, as with Xcode 4.3 and later (below), the command line tools required for the build process are not installed automatically and require an additional manual step to install the tools through Xcode's preferences.
Note: MacPorts 2.3.0 will print a warning if the command line tools are missing and advise you how to install them. On systems below 10.9, the message should read:
The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. You can install them from Xcode's Preferences in the Downloads section. See http://guide.macports.org/chunked/installing.xcode.html#installing.xcode.lion.43 for more information.
Missing Command Line Tools
Xcode 4.3 and later do not include a fully working set of command line tools by default. Starting with Mavericks, shims in /usr/bin will check for an Xcode installation and automatically use the tools provided by it. In the first case, nothing will build, in the second case, most ports will build, but some will fail because they expect headers to be located in /usr/include (which is empty or doesn't exist when the command line tools aren't installed).
On systems earlier than 10.9 you must open Xcode, go to Preferences, and download this component from the Downloads section. You will require an Apple ID to download the component. Starting with Mavericks you can install the command line tools by executing xcode-select --install on the command line.
Note: MacPorts 2.3.0 will print a warning if the command line tools are missing and advise you how to install them. The message will read:
The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build.
The message will advise you how to install the missing tools, on 10.9:
Install them by running `xcode-select --install'.
On Mountain Lion and below:
You can install them from Xcode's Preferences in the Downloads section. See http://guide.macports.org/chunked/installing.xcode.html#installing.xcode.lion.43 for more information.