new setuid error

Mr. Puneet Kishor punk.kish at gmail.com
Sat Aug 11 06:46:43 PDT 2012


On Aug 10, 2012, at 8:04 PM, Ryan Schmidt <ryandesign at macports.org> wrote:

> 
> On Aug 10, 2012, at 19:59, Puneet Kishor <punk.kish at gmail.com> wrote:
> 
>> I am on Mountain Lion, and have upgraded to Xcode 4.4. I get the following error
>> 
>> $sudo port selfupdate
>> dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid
> 
> This message lets you know that you have set DYLD_ environment variables, and that they are being ignored. It's usually an error to set DYLD_ environment variables at all anyway, so you might want to consider removing them from your environment.
> 
>> --->  Updating MacPorts base sources using rsync
>> MacPorts base version 2.1.1 installed,
>> MacPorts base version 2.1.2 downloaded.
>> --->  Updating the ports tree
>> --->  MacPorts base is outdated, installing new version 2.1.2
>> Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl
>> 
>> Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed
>> 
>> 
>> 
>> This is new. What could I do to set this right?
> 
> Run selfupdate with the -d flag so that we can see why it failed.
> 
> sudo port -d selfupdate
> 


checking for defaults... /usr/bin/defaults
checking for xcode-select... /usr/bin/xcode-select
checking Mac OS X version... 10.8
checking Xcode location... /Applications/Xcode.app/Contents/Developer
checking Xcode version... 4.4.1
checking for gcc... /usr/bin/cc
checking whether the C compiler works... no
configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base':
configure: error: C compiler cannot create executables
See `config.log' for more details
Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1
Exit code: 77
DEBUG: Error installing new MacPorts base: command execution failed
   while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed


So, it seems there is no `/usr/bin/cc`. I have no idea how this happened as I have, for the past several months now, installed lots of macport packages successfully.

As I noted in my OP, I did upgrade to Mountain Lion, and therefore, to Xcode 4.4. Could that be a cause?


--
Puneet Kishor


More information about the macports-users mailing list