Tell me more ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.
up vote 1 down vote favorite

I've just installed Mountain Lion, Xcode 4.4.1 + command line tools, and MacPorts for ML.

It's working for other packages but I can't get figlet to install.

When I use sudo port install figlet in the terminal it stops quickly and outputs:

--->  Building figlet
Error: org.macports.build for port figlet returned: command execution failed
Please see the log file for port figlet for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_figlet/figlet/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port figlet failed
share|improve this question
I'm not really sure what to look for in the log – Jack Stewart Aug 12 '12 at 6:37
I don't see any recent activity for figlet in MacPorts tracker. Only looking at the log will help. Can you post it to Pastebin--or something of the like--and link it in your question? – ephsmith Aug 12 '12 at 15:15
1  
heres the log: pastebin.com/W65fsC83 – Jack Stewart Aug 12 '12 at 15:27
1  
I noticed that in ML, Xcode doesn't create a 'Developer' directory, it holds everything in the Xcode app in the Applications folder. Could that have something to do with it? – Jack Stewart Aug 12 '12 at 15:29
1  
let us continue this discussion in chat – ephsmith Aug 12 '12 at 16:29
show 4 more comments

1 Answer

up vote 1 down vote accepted

I figured this out by cleaning the port with 

sudo port clean figlet

then installing using 

sudo port install figlet

According to the Macports ProblemHotList, this error is typical of existing packages that have stored compiler locations that aren't current. Cleaning the package and reinstalling assures the package is rebuilt with the current compiler collection settings for MacPorts.

share|improve this answer
Cleaning and trying again is the first thing you should always try anytime any MacPorts port fails to build, especially when the words "Skipping completed" are present in the main.log which indicate that the build attempt was not from a clean slate. – ryandesign Aug 13 '12 at 23:13

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.