#33094: libiconv: hangs during configure ------------------------------------+--------------------------------------- Reporter: duncanharris@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: tiger | Port: libiconv ------------------------------------+--------------------------------------- Changes (by ryandesign@…): * keywords: libiconv tiger => tiger * owner: macports-tickets@… => ryandesign@… * cc: ryandesign@…, duncanharris@… (removed) Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/33094#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#33094: libiconv: hangs during configure ------------------------------------+--------------------------------------- Reporter: duncanharris@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: tiger | Port: libiconv ------------------------------------+--------------------------------------- Comment(by 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 [wiki:UsingTheRightCompiler 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? -- Ticket URL: <https://trac.macports.org/ticket/33094#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#33094: libiconv: hangs during configure ------------------------------------+--------------------------------------- Reporter: duncanharris@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: tiger | Port: libiconv ------------------------------------+--------------------------------------- Comment(by duncanharris@…): sorry should have previewed first... destiny:/opt/local duncan$ which cc[[BR]] /usr/bin/cc[[BR]] destiny:/opt/local duncan$ cc[[BR]] cc: no input files[[BR]] destiny:/opt/local duncan$ cc -v[[BR]] Using built-in specs.[[BR]] Thread model: posix[[BR]] gcc version 3.3 20030304 (Apple Computer, Inc. build 1819)[[BR]] destiny:/opt/local duncan$ gcc -v[[BR]] Using built-in specs.[[BR]] Thread model: posix[[BR]] gcc version 3.3 20030304 (Apple Computer, Inc. build 1819)[[BR]] destiny:/opt/local duncan$ -- Ticket URL: <https://trac.macports.org/ticket/33094#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#33094: libiconv: hangs during configure ------------------------------------+--------------------------------------- Reporter: duncanharris@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: tiger | Port: libiconv ------------------------------------+--------------------------------------- Comment(by 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. [[BR]] Duncan. -- Ticket URL: <https://trac.macports.org/ticket/33094#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS