port selfupdate failed: Error installing new MacPorts base: shell command failed - THE SEQUEL

[kelly@…]

This might superficially seem similar to ​http://trac.macports.org/ticket/36432, but it's not the same - I tried all that already. I DO have xcode tools installed, as well as the latest XCode, and ALL software on my machine that's in the App Store is currently up-to-date.

! uname -a
Darwin [username] 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64

It seems that my curl is messed up ever since I updated to Mountain Lion - it worked fine before then. I have been trying everything imaginable to fix it, and was going to try to reinstall via MacPorts, hence this bug report. Here are the current curl results:

! which curl
/usr/bin/curl

Found an article on stackexchange saying to reinstall curl using MacPorts and when I tried it failed, saying my ports needed to be updated. So I tried doing this as well.

! sudo port selfupdate -v
--->  Updating the ports tree
--->  Updating MacPorts base sources using rsync
MacPorts base version 1.9.2 installed,
MacPorts base version 2.2.1 downloaded.
--->  MacPorts base is outdated, installing new version 2.2.1
Installing new MacPorts release in /opt/local as root:admin; permissions 0777; Tcl-Package in /Library/Tcl

Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed (see log for details)

NOTE: I can't even FIND the log in Mavericks!! And when I search the net I get conflicting reports on this as well! It's driving me crazy, honestly. Plus I feel as dumb as the dumbest dumb thing.

--AND--

! sudo port install pv
Password:
Error: Unable to open port: invalid command name "compiler.blacklist-append"
Error: Unable to execute port: upgrade gettext failed
To report a bug, see <http://guide.macports.org/#project.tickets>

--AND--

! sudo port install curl
Error: Unable to open port: can't read "subport": no such variable
To report a bug, see <http://guide.macports.org/#project.tickets>

Clearly, things are a huge mess, and I REALLY can't afford to start over with a complete clean Mountain Lion / Mavericks install. I'm a developer for a living and it would take at least 10+ hours to recreate everything in my environment. SO - any help appreciated.

Thank you, kbell

[neverpanic (Clemens Lang)]

You don't need to Cc yourself.

Your version is MacPorts is 1.9.2, which is really really old. That also explains the errors you see when you try to install some ports: These ports need features added in later versions of MacPorts.

We need to figure out why MacPorts fails to build (and thus update itself) on your system. Please run sudo port -d selfupdate, copy the output to a textfile and attach that.

[kelly@…]

Replying to cal@…:

I attached a file and also a pastebin (below)

​http://pastebin.com/sfEqbL5Q

[kelly@…]

Also, FWIW, I have been using an alternate coding environment almost this whole time, which is why I didn't update before now. With Lion, my MySQL got SO screwed up (there were "fixes" all over the Net, and then there were tons of people who never could get it fixed, like me) - so I stopped using my local dev environment altogether and used a clean VM, instead. Then Mountain Lion came along and fixed the MySQL bug (finally). But by then, I was pretty comfy in my VM and didn't bother switching.

Now, however, I have to get my local dev sitch sorted because I'm beta-testing a new product for a friend and it runs on all my local stuff. So here I am - trying to update MacPorts in hopes it will fix my curl problem (and install pipe viewer, etc...).

Thanks for the help!

[neverpanic (Clemens Lang)]

It seems there is a problem with your C compiler. Can you attach /opt/local/var/macports/sources/rsync.macports.org/release/base/config.log?

[kelly@…]

Clearly you're on the right track... (I ran nano and it was empty, and didn't exist unless I saved it - no overwrite prompt).

Also, I am hearing a lot of stuff about the paths being changed in Mavericks, and that previous bash profiles (especially $PATH settings) aren't being honored (​http://apple.stackexchange.com/questions/107441/os-x-mavericks-bash-profile-paths-dont-work. I wonder if this is ALSO part of the problem. None of this stuff was happening until Mavericks - the ONLY problem I was having before Mavericks was with curl...

[danielluke (Daniel J. Luke)]

Did you run xcode-select --install after installing Mavericks?

[kelly@…]

Replying to dluke@…:

Did you run xcode-select --install after installing Mavericks?

yes (this was 4.5 hours ago now):

! xcode-select --install
xcode-select: note: install requested for command line developer tools

...then it ran without problems, and returned me to the bash prompt. I saw the instructions regarding this in your post (though I thought I had run it after installing Mavericks the day it was released, but I must not have), so I ran it today, after the first attempt at self-update failed.

I did update XCode immediately after I installed Mavericks, along with all the other updates indicated by the AppStore at that time.

[neverpanic (Clemens Lang)]

The same or a similar issue was probably happening before Mavericks, or you wouldn't still be at MacPorts 1.9.2.

If there is no /opt/local/var/macports/sources/rsync.macports.org/release/base/config.log, please run sudo port -d selfupdate again and check again. The step that failed should have created this file in this directory.

If that doesn't help either, run

cd /opt/local/var/macports/sources/rsync.macports.org/release/base && PATH=/bin:/usr/bin CC=/usr/bin/llvm-gcc-4.2 ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0777 --enable-readline

and check for the file again.

[kelly@…]

failed again, same point (the Tcl library?). Ran the second command:

! sudo cd /opt/local/var/macports/sources/rsync.macports.org/release/base && PATH=/bin:/usr/bin CC=/usr/bin/llvm-gcc-4.2 ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0777 --enable-readline
./configure: line 2292: config.log: Permission denied
./configure: line 2302: config.log: Permission denied

File is still listing as a NEW FILE in nano...

Should I repair permissions and try again? I've done it already once since Mavericks update, but this sure looks like a likely candidate...

[neverpanic (Clemens Lang)]

No, the problem is configure couldn't write config.log because of a permission problem. Solution is to add sudo at the right place. Use:

cd /opt/local/var/macports/sources/rsync.macports.org/release/base && sudo env PATH=/bin:/usr/bin CC=/usr/bin/llvm-gcc-4.2 ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0777 --enable-readline

[kelly@…]

ah, ok sure. Here is the result:

! cd /opt/local/var/macports/sources/rsync.macports.org/release/base && sudo env PATH=/bin:/usr/bin CC=/usr/bin/llvm-gcc-4.2 ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0777 --enable-readline
Password:
checking build system type... i386-apple-darwin13.0.0
checking host system type... i386-apple-darwin13.0.0
checking target system type... i386-apple-darwin13.0.0
checking MacPorts version... 2.2.1
checking for sw_vers... /usr/bin/sw_vers
checking for defaults... /usr/bin/defaults
checking for xcode-select... /usr/bin/xcode-select
checking Mac OS X version... 10.9
checking Xcode location... /Applications/Xcode.app/Contents/Developer
checking Xcode version... 5.0.1
checking for gcc... /usr/bin/llvm-gcc-4.2
checking whether the C compiler works... no
configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/base':
configure: error: C compiler cannot create executables
See `config.log' for more details

[neverpanic (Clemens Lang)]

Now check for /opt/local/var/macports/sources/rsync.macports.org/release/base/config.log and attach it.

[neverpanic (Clemens Lang)]

The problem seems to be

./configure: line 3342: /usr/bin/llvm-gcc-4.2: No such file or directory

Can you grab the binary installer for Mavericks from ​https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg and run it? That's probably easier than running the necessary commands manually.

The problem seems to be that your version of MacPorts used to use llvm-gcc-4.2 to build itself – however, Mavericks removed this compiler, causing your selfupdate to fail.

[neverpanic (Clemens Lang)]

After you've done that, verify that sudo port -df selfupdate works.

[kelly@…]

Replying to cal@…:

After you've done that, verify that sudo port -df selfupdate works.

I never in a million years would have figured that out, so thank you SO much!! It's installing now, taking a few minutes here (it's been stuck at about 85% for a few minutes). I'll report back as soon as it's done and I try the selfupdate. It says "less than a minute" remaining, but it's been that way for over 10 minutes now...

[kelly@…]

Any idea on what the upper limit of this install timing should be? It's at just under 20 minutes now, and still hung on the very last bit. It asked for permissions to the rsync folder (which I granted), and that was the last bit of progress made. The progress bar hasn't moved from this spot in over 15 minutes. Advice?

[neverpanic (Clemens Lang)]

Take a look at the installer log (press command+L). If you see new output coming up, leave it running, it might actually take quite a while. Apple's installer tells users this is only going to take a minute, but that's not true and we have no influence over that.

[kelly@…]

Believe it or not, it was hung on a problem I would never have seen if I hadn't opened the Console and taken a look... you have to accept the XCode LICENSE - VIA THE TERMINAL - can you believe? It's a totally separate process!

SO, once I ran through the prompts and typed "agree" at the end of this command:

sudo xcodebuild -license

the installer finally completed.

I ran the selfupdate, and "Congratulations, you have successfully upgraded the MacPorts system." YAY!!!

[kelly@…]

I'm running

port upgrade outdated

now; this might take awhile...

You're a saint - thank you so much!

[neverpanic (Clemens Lang)]

That would also explain why the selfupdate was not working before that. Glad you got it working.

Since you probably just updated to Mavericks, also take a look at wiki:Migration.

The core issue you had, that updating from 1.9.2 on Mavericks does not work due to /usr/bin/llvm-gcc-4.2 being used as a compiler can no longer be fixed by us, though. I'm thus closing this ticket wontfix.

[kelly@…]

UNDERSTOOD! Hopefully though, someone else will be able to benefit from our day's toil. Thanks again! Cheers, Kelly

[kelly@…]

opened new ticket and deleted comment in this thread. #41370