Opened 14 years ago

Closed 13 years ago

#25862 closed defect (worksforme)

libiconv configure failure when libintl is corrupted

Reported by: davidh@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc:
Port: libiconv

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I just performed a successful port selfupdate to 1.9.2, found I needed new libiconv.

wilder-hendersons-macbook-pro-2:~ davidh$ sudo port clean libiconv
--->  Cleaning libiconv
wilder-hendersons-macbook-pro-2:~ davidh$ sudo port install libiconv
--->  Computing dependencies for libiconv
--->  Fetching libiconv
--->  Verifying checksum(s) for libiconv
--->  Extracting libiconv
--->  Applying patches to libiconv
--->  Configuring libiconv
Error: Target org.macports.configure returned: configure failure: shell command failed
Log for libiconv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libiconv/main.log
Error: Status 1 encountered during processing.

Attachments (1)

main.log (15.3 KB) - added by davidh@… 14 years ago.
main.log when attempting install of libiconv

Download all attachments as: .zip

Change History (7)

comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Milestone: MacPorts 1.9.2
Owner: changed from macports-tickets@… to ryandesign@…
Port: libiconv added
Summary: shell error installing libiconvlibiconv configure failure

Remember to use WikiFormatting and to Cc the port's maintainer (that's me in this case).

Do not set the Milestone field for port tickets.

MacPorts 1.9.2 does not exist yet; presumably you meant you selfupdated to 1.9.1

Please attach the referenced logfile so we can see what went wrong.

Changed 14 years ago by davidh@…

Attachment: main.log added

main.log when attempting install of libiconv

comment:2 in reply to:  description Changed 14 years ago by davidh@…

Replying to davidh@…:

I just performed a successful port selfupdate to 1.9.1, found I needed new libiconv.

wilder-hendersons-macbook-pro-2:~ davidh$ sudo port clean libiconv
--->  Cleaning libiconv
wilder-hendersons-macbook-pro-2:~ davidh$ sudo port install libiconv
--->  Computing dependencies for libiconv
--->  Fetching libiconv
--->  Verifying checksum(s) for libiconv
--->  Extracting libiconv
--->  Applying patches to libiconv
--->  Configuring libiconv
Error: Target org.macports.configure returned: configure failure: shell command failed
Log for libiconv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libiconv/main.log
Error: Status 1 encountered during processing.

comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Ok, the relevant lines are:

:info:configure dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
:info:configure   Referenced from: /opt/local/bin/gawk
:info:configure   Reason: no suitable image found.  Did find:
:info:configure         /opt/local/lib/libintl.8.dylib: unknown file type, first eight bytes: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

Your gettext library (libintl.dylib) appears to have exploded so you will have to rebuild gettext. Before you do so you should uninstall gawk, because otherwise gettext's build will try to use gawk, which, as we see above, doesn't work.

sudo port -f uninstall gawk
sudo port clean gettext
sudo port -n upgrade --force gettext

You might run into similar problems with gsed and grep; if so, uninstall them too before attempting to rebuild gettext.

comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Did that work?

comment:5 Changed 13 years ago by myork@…

I had this same issue. I removed and reinstalled gawk using porticus - this seemed to correct the issue.

comment:6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: worksforme
Status: newclosed
Summary: libiconv configure failurelibiconv configure failure when libintl is corrupted

If just removing and reinstalling gawk fixed the issue, then it's not the same as in this ticket, which is about a gettext libintl library that got corrupted somehow.

Since we haven't heard from the reporter in half a year, I'm going to assume he got it working by rebuilding gettext.

Note: See TracTickets for help on using tickets.