Upgrade coreutils failed - Leopard

Michael Hernandez sequethin at gmail.com
Wed Oct 31 11:06:54 PDT 2007


On Oct 31, 2007, at 1:50 PM, Thorsten Zörner wrote:

> MacBook Pro, Intel CoreDuo, 2 GHz, MacOS 10.5, MacPorts 1.520
>
>
> Just got my Leopard installed yesterday,
> checking for outdated ports... coreutils
> Fine so far, then this happens:
>
> Macintosh:~ thorsten$ sudo port upgrade coreutils
> Password:
> --->  Configuring coreutils
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_sysutils_coreutils/work/coreutils-6.9"  
> && ./configure --prefix=/opt/local --program-prefix=g --disable-nls  
> " returned error 77
> Command output: checking build system type... i386-apple-darwin9.0.0
> checking host system type... i386-apple-darwin9.0.0
> configure: autobuild project... GNU coreutils
> configure: autobuild revision... 6.9
> configure: autobuild hostname... Macintosh.local
> configure: autobuild timestamp... 20071031-184539
> checking for a BSD-compatible install... /opt/local/bin/ginstall -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
>
> Error: Unable to upgrade port: 1
> Macintosh:~ thorsten$
>
> What seems to be the problem?
> Cheers, Thorsten.
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users


do you have any environment vars like CFLAGS set? that might be the  
culprit. Check the config.log to see where the gcc test is failing.

--Mike H




More information about the macports-users mailing list