Opened 9 years ago

Closed 9 years ago

#30545 closed defect (invalid)

Update of MacPorts base to version 2.0.1 fails

Reported by: michelle.lynn.gill@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.0.1
Keywords: Cc:
Port:

Description

Just attempted to selfupdate MacPorts and the update fails when attempting to install version 2.0.1 of MacPorts base. The output of port -d selfupdate is below, but the relevant portion seems to involve a failure to find a working C compiler.

I tried switching the compiler to both llvm-gcc42 and gcc42 (the ones from XCode) just in case the issue arose from having my default compiler set to one provided by MacPorts. In both cases, the error generated was the same.

According to the debugging output, there is a log file. I searched recursively through my MacPorts install and couldn't find it. If someone tells me where it is, I'm happy to post it.

I'm on Lion using XCode 4.1.

% sudo port -d selfupdate              
--->  Updating the ports tree
DEBUG: Synchronizing ports tree(s)
Synchronizing local ports tree from file:///Volumes/Files/macports/build
Creating port index in /Volumes/Files/macports/build

Total number of ports parsed:	0 
Ports successfully parsed:	0 
Ports failed:			0 
Up-to-date ports skipped:	1

Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar
DEBUG: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs
receiving file list ... done

sent 36 bytes  received 70 bytes  70.67 bytes/sec
total size is 44920320  speedup is 423776.60
DEBUG: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar.rmd160 /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs
receiving file list ... done

sent 36 bytes  received 77 bytes  226.00 bytes/sec
total size is 512  speedup is 4.53
DEBUG: successful verification with key /Volumes/Files/macports/share/macports/macports-pubkey.pem
DEBUG: /usr/bin/tar -C /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/tmp -xf /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/ports.tar
Creating port index in /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/ports

Total number of ports parsed:	0 
Ports successfully parsed:	0 
Ports failed:			0 
Up-to-date ports skipped:	8257

DEBUG: MacPorts sources location: /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs
--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  70.00 bytes/sec
total size is 3219456  speedup is 30661.49
receiving file list ... done

sent 36 bytes  received 76 bytes  224.00 bytes/sec
total size is 512  speedup is 4.57
DEBUG: successful verification with key /Volumes/Files/macports/share/macports/macports-pubkey.pem
DEBUG: /usr/bin/tar -C /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/tmp -xf /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/base.tar
MacPorts base version 2.0.0 installed,
DEBUG: Rebuilding and reinstalling MacPorts if needed
MacPorts base version 2.0.1 downloaded.
--->  MacPorts base is outdated, installing new version 2.0.1
DEBUG: Permissions OK
Installing new MacPorts release in /Volumes/Files/macports as root:admin; permissions 0755; Tcl-Package in /Volumes/Files/macports/Library/Tcl

checking build system type... i386-apple-darwin11.0.0
checking host system type... i386-apple-darwin11.0.0
checking target system type... i386-apple-darwin11.0.0
checking MacPorts version... 2.0.1
checking for sw_vers... /usr/bin/sw_vers
checking for defaults... /usr/bin/defaults
checking for xcode-select... no
checking Mac OS X version... 10.7
checking Xcode version... 4.1
checking for gcc... /usr/bin/cc
checking whether the C compiler works... no
configure: error: in `/Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/base':
configure: error: C compiler cannot create executables
See `config.log' for more details
shell command "cd /Volumes/Files/macports/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc ./configure --prefix=/Volumes/Files/macports --with-tclpackage=/Volumes/Files/macports/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install" returned error 77
DEBUG: Error installing new MacPorts base: shell command failed (see log for details)
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /Volumes/Files/macports/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed (see log for details)

Change History (8)

comment:1 Changed 9 years ago by jmroot (Joshua Root)

Does /usr/bin/cc work outside of MacPorts?

comment:2 in reply to:  1 Changed 9 years ago by michelle.lynn.gill@…

Replying to jmr@…:

Does /usr/bin/cc work outside of MacPorts?

Yes, I should have mentioned that /usr/bin/cc runs fine--I was using it just the other day. To check again, I just wrote a "hello world" program and compiled it by calling the full path for /usr/bin/cc. The compiled binary runs fine.

comment:3 Changed 9 years ago by michelle.lynn.gill@…

Ugh, I just realized you're right--/usr/bin/cc doesn't work anymore. I was logged into a different computer when I mentioned using /usr/bin/cc successfully.

This weekend, I reinstalled Lion over my existing install because I had inadvertently nuked Lion's recovery partition. I suspect this removed the command line tools (i.e. /usr/bin/cc), even though it seems to have left XCode itself untouched. I'm reinstalling XCode right now. I will update shortly.

comment:4 in reply to:  3 Changed 9 years ago by michelle.lynn.gill@…

Replying to michelle.lynn.gill@…:

Ugh, I just realized you're right--/usr/bin/cc doesn't work anymore. I was logged into a different computer when I mentioned using /usr/bin/cc successfully.

This weekend, I reinstalled Lion over my existing install because I had inadvertently nuked Lion's recovery partition. I suspect this removed the command line tools (i.e. /usr/bin/cc), even though it seems to have left XCode itself untouched. I'm reinstalling XCode right now. I will update shortly.

Reinstalling XCode fixed the issue of the missing command line tools. I apologize for not realizing this before filing a ticket. If XCode had also been missing, the problem would have been obvious.

My upgrade to MacPorts 2.0.1 worked after the XCode reinstall.

Thanks

comment:5 Changed 9 years ago by jmroot (Joshua Root)

Resolution: invalid
Status: newclosed

comment:6 Changed 9 years ago by davidfavor (David Favor)

Resolution: invalid
Status: closedreopened

This is still failing.

After upgrading to 2.0.1 on Snow no packages compile.

I've reinstalled Xcode-3.2.6 and still fails.

Did full Macports remove and reinstall from scratch and still fails.

Log attached.

comment:7 Changed 9 years ago by davidfavor (David Favor)

No packages might be incorrect.

My install script starts by installing perl and this fails.

Perl is required by many packages, so this is a show stopper.

comment:8 Changed 9 years ago by jmroot (Joshua Root)

Resolution: invalid
Status: reopenedclosed

That's a completely different problem than the one described in this ticket. Open a new ticket, and attach the debug log.

Note: See TracTickets for help on using tickets.