Opened 9 years ago

Closed 9 years ago

#47857 closed defect (worksforme)

macports hangs configuring ghostscript while checking for gcc

Reported by: DavidSagan (David Sagan) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port:

Description

See the attached log file. The last line of the file is:

checking for gcc... /usr/bin/clang

macports hangs here (over half a day). Using OS 10.10.3 "which gcc" gives:

/opt/local/bin/gcc

And: mc66:~/Bmad/bmad_dist/regression_tests> gcc --version

gcc (MacPorts gcc48 4.8.4_0) 4.8.4

Using macports version 2.3.3 Using Xcode version 6.3.2

What to do?

Attachments (1)

log.txt (52.8 KB) - added by DavidSagan (David Sagan) 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by DavidSagan (David Sagan)

Attachment: log.txt added

comment:1 in reply to:  description Changed 9 years ago by DavidSagan (David Sagan)

Also the command that macports hung on is:

sudo port -d -v upgrade outdated

comment:4 Changed 9 years ago by neverpanic (Clemens Lang)

We've seen a couple of these recently, and somehow, there's always some standard process hanging for reasons we do not understand. In your case it's probably the check after the clang one (which probably checks whether the compiler actually works). Finding out what goes wrong here involves low-level debugging which nobody had the time to do yet (or is capable of).

We're speculating the issue may be due to Gatekeeper, but we really don't know. In any case, so far rebooting has always fixed it, even though that seems like a very Windows-y approach to things.

comment:5 in reply to:  4 Changed 9 years ago by DavidSagan (David Sagan)

Replying to cal@…:

We've seen a couple of these recently, and somehow, there's always some standard process hanging for reasons we do not understand. In your case it's probably the check after the clang one (which probably checks whether the compiler actually works). Finding out what goes wrong here involves low-level debugging which nobody had the time to do yet (or is capable of).

We're speculating the issue may be due to Gatekeeper, but we really don't know. In any case, so far rebooting has always fixed it, even though that seems like a very Windows-y approach to things.

A reboot did fix the problem. Thanks!

comment:6 Changed 9 years ago by neverpanic (Clemens Lang)

Resolution: worksforme
Status: newclosed

Great! Glad you could fix it. Eventually, we'll figure out what the problem is.

Note: See TracTickets for help on using tickets.