libiconv: hangs during configure

[duncanharris@…]

Trying to install libiconv and it sems to hang part way through the install (I left it running overnight just to make sure I wasn't being impatient, after which I killed it). Log file attached (main.log.gz) and console output attached (console.log).

MacBook Pro (Intel) / OS 10.4.11 / XCode 2.5

Thanks for your help, Duncan

[duncanharris@…]

libiconv log output

[duncanharris@…]

Console output from port command

[ryandesign@…]

The main.log is incomplete so it doesn't show anything wrong.

The console.log shows you cancelled it after it successfully located ranlib:

checking for ranlib... ranlib

I'll have to check on my Tiger Mac what it's supposed to do after checking for ranlib.

[duncanharris@…]

Quick update; I tried uninstalling and reinstalling macports from scratch from the tiger dmg but still get the same problem. Also noticed that when I try to install a port that depends on libiconv, such as bash for example, I also get that same problem.

Any luck checking your Tiger Mac?

[ryandesign@…]

The next thing in my log after the ranlib line is:

checking whether /usr/bin/gcc-4.0 and cc understand -c and -o together... yes

Earlier tests in the configure script already succeeded at using /usr/bin/gcc-4.0, so perhaps it's the test of cc here that's the problem. It's unclear to me why the configure script is testing cc at all, since we never want to use cc anyway, but that is the way autoconf is doing it. What is "cc" on your system? Use "which cc" to find out. What happens if you run "cc" yourself on the command line -- does it also hang?

[duncanharris@…]

no it doesn't hang;

destiny:/opt/local duncan$ which cc    
/usr/bin/cc
destiny:/opt/local duncan$ cc
cc: no input files
destiny:/opt/local duncan$ cc -v
Using built-in specs.
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1819)
destiny:/opt/local duncan$ gcc -v
Using built-in specs.
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1819)
destiny:/opt/local duncan$

[ryandesign@…]

Nevertheless, it gives us a clue: on Tiger, cc should be gcc 4.0, not 3.3. Try uninstalling and reinstalling Xcode 2.5 to set things right.

[duncanharris@…]

Problem solved. Symlinks in /usr/bin were pointing to gcc-3.0 rather than gcc-4.0. Reinstalled xcode as suggested and libiconv installed first time. Many thanks for your help, much appreciated.
Duncan.

[ryandesign@…]

Great, glad you got it solved.