Opened 11 years ago

Closed 11 years ago

#40340 closed defect (invalid)

gettext configure step hangs

Reported by: luc-j-bourhis (Luc J. Bourhis) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc:
Port: gettext

Description

~> sudo port install gettext @0.18.3.1_0+universal
--->  Computing dependencies for gettext
--->  Fetching archive for gettext
--->  Attempting to fetch gettext-0.18.3.1_0+universal.darwin_11.i386-x86_64.tbz2 from http://lil.fr.packages.macports.org/gettext
--->  Attempting to fetch gettext-0.18.3.1_0+universal.darwin_11.i386-x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/gettext
--->  Attempting to fetch gettext-0.18.3.1_0+universal.darwin_11.i386-x86_64.tbz2 from http://packages.macports.org/gettext
--->  Fetching distfiles for gettext
--->  Verifying checksums for gettext
--->  Extracting gettext
--->  Applying patches to gettext
--->  Configuring gettext

The installation hangs there: no printout, nothing. This is on MacOS 10.7.5.

Change History (3)

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

Owner: changed from macports-tickets@… to ryandesign@…
Port: @0.18.3.1_0+universal removed

How long did you wait? The gettext configure phase does take longer than some other ports', because it's running several configure scripts one after another.

Does the log say anything about that it's doing? Or, have you tried installing in verbose mode (sudo port -v install gettext) to get more output?

Version 0, edited 11 years ago by ryandesign (Ryan Carsten Schmidt) (next)

comment:2 Changed 11 years ago by luc-j-bourhis (Luc J. Bourhis)

It hangs at seemingly random places. And it works fine if using a clone of the same macport install on another disk. Please forgive the noise then, it looks like a hardware problem out-of-the-blue.

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

Resolution: invalid
Status: newclosed

Hmm, hope you figure out what's causing it! You've probably already verified the disk in Disk Utility, checked the SMART status, checked for bad RAM...

Note: See TracTickets for help on using tickets.