#39426 closed defect (duplicate)
MacPorts doesn't install on Mavericks
Reported by: | igeek1@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.1.3 |
Keywords: | Cc: | dr-evil-lob@…, razzfazz (Daniel Becker), dm@…, pkutzner+macports@…, bonoba@…, suominen (Kimmo Suominen), ian@…, jeremy@…, eirnym (Eir Nym), MaddTheSane (C.W. Betts), joelburton (Joel Burton), macports@…, robsonpeixoto@…, jrblevin@…, bhadder@… | |
Port: |
Description
Didn't see a bug, so I thought I would put one in. It doesn't install on the Mavericks seed from WWDC. Couldn't get it to build from source, either.
Change History (24)
comment:1 Changed 11 years ago by mf2k (Frank Schima)
Keywords: | OS X build install removed |
---|---|
Priority: | High → Normal |
comment:2 Changed 11 years ago by neverpanic (Clemens Lang)
There's not much we can do about this (at least those of us without access to Mavericks). Posting details on this would probably violate your NDA. See also https://lists.macosforge.org/pipermail/macports-dev/2013-June/022942.html.
comment:3 Changed 11 years ago by jpr5@…
MacPorts won't build because Tcl.framework
is moving from Mavericks' system libraries to be inside of Xcode proper. This necessitates specifying --with-tcl
and --with-tclinclude
options to MacPorts' configure
.
On Mavericks DP3 with Xcode5-DP4 installed:
curl -O https://distfiles.macports.org/MacPorts/MacPorts-2.2.0.tar.bz2 tar jxvf MacPorts-2.2.0.tar.bz2 cd MacPorts-2.2.0 CC=/usr/bin/cc ./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline \ --with-tclpackage=/Library/Tcl \ --with-tcl=/Applications/Xcode5-DP4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework \ --with-tclinclude=/Applications/Xcode5-DP4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework/Headers make make install
Follow the basic instructions to clean out your existing MacPorts installation. Trying to install MacPorts over an existing install quickly turns into a nightmare, around libs like libiconv
and libintl
, etc. Keep in mind it won't just be as easy as wiping /opt/local/
-- things like launchd
files and other things outside of the /opt/local
root may still linger, which will stop MacPorts and require you to port -f activate ...
individual packages to proceed each time.
comment:14 Changed 11 years ago by eirnym (Eir Nym)
Mavericks is out. And it's free. So can be macports installed?
comment:17 Changed 11 years ago by jmroot (Joshua Root)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Type: | enhancement → defect |
comment:21 Changed 11 years ago by neverpanic (Clemens Lang)
Please see comment:16:ticket:40476 everyone. Especially do not attempt to use the method described above, it is not necessary. A binary installer for Mavericks will be available in a few days.
comment:23 follow-up: 24 Changed 11 years ago by craig@…
Replying to bhadder@…:
Cc Me!
If you can't wait a few days, you should know that the locations have changed slightly with the release. Here are the runes to build 2.2.0 from source tonight:
./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline --with-tclpackage=/Library/Tcl --with-tcl=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework/Versions/Current --with-tclinclude=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework/Versions/Current/Headers
comment:24 Changed 11 years ago by neverpanic (Clemens Lang)
Replying to craig@…:
If you can't wait a few days, you should know that the locations have changed slightly with the release. Here are the runes to build 2.2.0 from source tonight:
./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline --with-tclpackage=/Library/Tcl --with-tcl=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework/Versions/Current --with-tclinclude=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Tcl.framework/Versions/Current/Headers
Please don't do that and instead just read comment:16:ticket:40476. You don't need to juggle with any special flags to ./configure
, just make sure you did run xcode-select --install
and use ./configure
without any parameters, which will work fine. You especially do not need to specify any Tcl paths, any paths within an SDK, or any paths at all.
Please do not set the Priority field.