Opened 9 years ago

Closed 9 years ago

#46799 closed defect (worksforme)

fltk-devel not building

Reported by: matthias@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port: fltk-devel

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

When I try to install fltk-devel, I get the following:

sudo port install fltk-devel
--->  Computing dependencies for fltk-devel
--->  Fetching archive for fltk-devel
--->  Attempting to fetch fltk-devel-1.3.x-r10542_0.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/fltk-devel
--->  Attempting to fetch fltk-devel-1.3.x-r10542_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/fltk-devel
--->  Attempting to fetch fltk-devel-1.3.x-r10542_0.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/fltk-devel
--->  Fetching distfiles for fltk-devel
--->  Verifying checksums for fltk-devel
--->  Extracting fltk-devel
--->  Applying patches to fltk-devel
--->  Configuring fltk-devel
--->  Building fltk-devel

Then it stays like this forever (I killed it after a few days).

Change History (4)

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

Description: modified (diff)
Keywords: fltk removed
Owner: changed from macports-tickets@… to michaelld@…

Please try again with the debug flag:

sudo port -d install fltk-devel

When it hangs, please show us the last few lines of output.

comment:2 Changed 9 years ago by michaelld (Michael Dickens)

Even better, do:

sudo port clean fltk-devel
sudo port selfupdate
sudo port -d install fltk-devel

and, then if it hangs cut the last few pages of the debug output & attach them here. You'll have the latest port version and we can maybe start debugging the issue.

comment:3 Changed 9 years ago by matthias@…

Ok, I tried this. No issues this time. It just worked. Hmmmm.

comment:4 Changed 9 years ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: newclosed

"Cruft happens": sometimes the system and/or port get into a naughty state. Rebooting often takes care of the issue; sometimes doing a Disk Utility permissions repair does. Sometimes getting port to clean itself up does too. MacPorts is an evolving project; what worked 6 months ago might not work today without updating due to Apple system updates. We try to keep on top of all of these, but we can't catch everything. Hence, "cruft happens". Thanks for reporting back!

Note: See TracTickets for help on using tickets.