MacPorts_Framework: build failed

[me@…]

karsten-harazims-macbook-pro:~ karstenharazim$ sudo port install pallet
--->  Computing dependencies for Pallet
--->  Dependencies to be installed: MacPorts_Framework
--->  Fetching archive for MacPorts_Framework
--->  Attempting to fetch MacPorts_Framework-1.2.1_1.darwin_12.x86_64.tbz2 from http://packages.macports.org/MacPorts_Framework
--->  Fetching distfiles for MacPorts_Framework
--->  Verifying checksum(s) for MacPorts_Framework
--->  Extracting MacPorts_Framework
--->  Configuring MacPorts_Framework
--->  Building MacPorts_Framework
Error: org.macports.build for port MacPorts_Framework returned: command execution failed
Error: Failed to install MacPorts_Framework
Please see the log file for port MacPorts_Framework for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/main.log
Error: The following dependencies were not installed: MacPorts_Framework
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port pallet failed


:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file so that we can see why the build failed. And remember to use WikiFormatting when writing in Trac.

[wrwolf2@…]

Cc Me!

[wrwolf2@…]

getting the same problem with same pallet installation attempt on a development system with Xcode 4.5DP3 . The new packaging format for xcode could be the problem . (on my system tho) i haven't downloaded xcode 4.4 then i have no clue about the package & installation location with os X 10.8 in those circumstances however, since Apple changed & included developer folder within the app (Xcode app) package content i started to get many errors. (i.e. Warning: xcodebuild exists but failed to execute : Warning: Xcode does not appear to be installed; most ports will likely fail to build)

marc

[ryandesign (Ryan Carsten Schmidt)]

We can't really help you if you're using preview versions of Xcode. karstenharazim, are you also using a preview of Xcode 4.5?

[wrwolf2@…]

installation problem sorted on me dev system. (marc - wrwolf2 AKA mcWolf2). pls feedback if not clear enough with STEPS to be rewritten.

• with this config : OS X 10.8 (build 12A269), xCode 4.5 DP3, java for os X - july '12 release (i only mention java because if remember well it is necessary for xcode to run or for some essential components then, i always install latest java release as a regular task). also installed xQuartz replacing os X X-11 native app & replaced Command Line Tools for xCode 4.5 DP3 os X 10.8 with C.L.T for xcode 4.4 os X 10.8 found @ ​https://developer.apple.com/downloads/index.action.

assuming then You have updated macport ("sudo port -v selfupdate" from terminal window) , i run "sudo port install pallet" & still got errors. had a look at log files & found that xcode license agreement has to be signed (AGREE) within terminal window also.-> type & run "xcodebuild -license" & follow instructions - scroll down- 'til the end of the agreement then type "agree" hit RETURN/ENTER key and you're done. ( suggesting to type & run from within ROOT account - LOGIN: root; PASSWD: yourRootPasswd - to make agreement accepted system wide) bare in mind You might have to select correct xCode release by typing " sudo xcode-select -switch /Applications/Xcode45-DP3.app/Contents/Developer # version 4.5 ", Mountain Lion (os X 10.8 ) DEVELOPER folder for Xcode.app, is located (installed) within the package content & it is not a folder on your system root <-top level parent directory> any longer. NOTE: when logging in as ROOT (in terminal) i cannot run PORT command , not even by navigating (changing directory) to /opt/local/bin & typing & running "PORT" (or PORT INSTALL PALLET). NOT A CLUE Y this happens for "PORT" command is there in bin directory, privileges are set as ROOT account & still no execution of "port" UNIX EXE file.(Lion 10.7 wasn't raising errors msgs.)

last but not least there's a minor bug to fix in Lion & Mountain Lion ( haven't tested on Snow Leopard). Blank Passwords (no password) for admin account are not accepted in terminal when running SUDO commands & the way around in Lion 10.7 is to login with ROOT (ROOT credentials) in terminal and execute commands without SUDO pre-fix. In ML (mountain lion, 10.8) however , PORT command won't run when logged in as ROOT as mentioned above. (i.e.: mcBook:bin root# port install pallet -sh: port: command not found) THEN set password to something & DO NOT leave BLANK passwords

[ryandesign (Ryan Carsten Schmidt)]

So basically you had to install the command line tools, select Xcode, and agree to the license agreement. Nothing we haven't documented in our ​Guide and Wiki.

Using sudo has always required the account's password to be non-blank; Apple has documented this in their knowledge base ​here.

[ryandesign (Ryan Carsten Schmidt)]

Not being able to find the port command while root suggests that you have not ​set up your shell environment for the root user.

[wrwolf2@…]

eventually apple is expecting far too much work from US - blank passwrds for main/admin users are pretty common on a stand alone dev system to avoid entering USER & PASSWORD each time we start-up (bootstrap) & switch on the laptop . had no clue about ROOT user shell environment, didn't have any problem in Lion (10.7). mcWolf2 (a.k.a wrwolf2ATaolDOTcom)

[davidrogers@…]

I'm having a similar issue but it appears to be server related.

version:1
:debug:main changing euid/egid - current euid: 0 - current egid: 0
:debug:main egid changed to: 502
:debug:main euid changed to: 502
:debug:main Executing org.macports.main (MacPorts_Framework)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.archivefetch (MacPorts_Framework)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:fetch fetch phase started at Mon Sep 17 01:43:28 CDT 2012
:notice:fetch --->  Fetching distfiles for MacPorts_Framework
:debug:fetch Executing org.macports.fetch (MacPorts_Framework)
:debug:fetch Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.8'
:debug:fetch Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927'
:debug:fetch Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927 2>&1
:info:fetch svn: Server sent unexpected return value (503 Service Temporarily Unavailable) in response to OPTIONS request for 'https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework'
:info:fetch Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927 2>&1
:info:fetch Exit code: 1
:error:fetch org.macports.fetch for port MacPorts_Framework returned: Subversion check out failed
:debug:fetch Error code: NONE
:debug:fetch Backtrace: Subversion check out failed
    while executing
"svnfetch"
    (procedure "portfetch::fetch_main" line 13)
    invoked from within
"$procedure $targetname"
:info:fetch Warning: targets not executed for MacPorts_Framework: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install
:error:fetch Failed to install MacPorts_Framework
:debug:fetch couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory
    while executing
"open [file join $dir tclIndex]"
:notice:fetch Please see the log file for port MacPorts_Framework for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_MacPorts_Framework/MacPorts_Framework/main.log

[vijay.santhanam@…]

I have a similar if not identical problem on Mountain Lion (I recently upgraded).

I ran the command

sudo port upgrade outdated

Here's the log macports told me it wrote to.

version:1
:msg:main --->  Computing dependencies for MacPorts_Framework:info:main .:debug:main MacPorts_Framework has no conflicts
:debug:main Searching for dependency: subversion
:debug:main Found Dependency: receipt exists for subversion
:msg:main 
:debug:main Executing org.macports.main (MacPorts_Framework)
:debug:main changing euid/egid - current euid: 0 - current egid: 0
:debug:main egid changed to: 502
:debug:main euid changed to: 503
:debug:main Skipping completed org.macports.archivefetch (MacPorts_Framework)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:fetch fetch phase started at Wed Sep 19 08:49:42 EST 2012
:notice:fetch --->  Fetching distfiles for MacPorts_Framework
:debug:fetch Executing org.macports.fetch (MacPorts_Framework)
:debug:fetch Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/MacPorts_Framework/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.8'
:debug:fetch Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927'
:debug:fetch Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927 2>&1
:info:fetch svn: Server sent unexpected return value (503 Service Temporarily Unavailable) in response to OPTIONS request for 'https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework'
:info:fetch Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/MacPorts_Framework/work" && /usr/bin/svn --non-interactive --trust-server-cert export https://svn.macosforge.org/repository/macports/contrib/MacPorts_Framework@86927 2>&1
:info:fetch Exit code: 1
:error:fetch org.macports.fetch for port MacPorts_Framework returned: Subversion check out failed
:debug:fetch Error code: NONE
:debug:fetch Backtrace: Subversion check out failed
    while executing
"svnfetch"
    (procedure "portfetch::fetch_main" line 13)
    invoked from within
"$procedure $targetname"
:info:fetch Warning: targets not executed for MacPorts_Framework: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install
:notice:fetch Please see the log file for port MacPorts_Framework for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_MacPorts_Framework/MacPorts_Framework/main.log

Any help is greatly appreciated.

Cheers, CVertex

[vijay.santhanam@…]

Cc Me!

[jmroot (Joshua Root)]

Closing as per comment:6 (comment:9 and later are not the same problem).