pidgin @2.10.7_1: Tcl development headers not found

[an0nym@…]

pidgin @2.10.7_1 +no_x11+quartz will not configure on Mavericks

$ sudo port clean pidgin && sudo port install pidgin +no_x11+quartz 
Password:
--->  Cleaning pidgin
--->  Computing dependencies for pidgin
--->  Fetching archive for pidgin
--->  Attempting to fetch pidgin-2.10.7_1+no_x11+quartz.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/pidgin
--->  Attempting to fetch pidgin-2.10.7_1+no_x11+quartz.darwin_13.x86_64.tbz2 from http://packages.macports.org/pidgin
--->  Attempting to fetch pidgin-2.10.7_1+no_x11+quartz.darwin_13.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/pidgin
--->  Fetching distfiles for pidgin
--->  Verifying checksums for pidgin
--->  Extracting pidgin
--->  Applying patches to pidgin
--->  Configuring pidgin
Error: Failed to configure pidgin, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_pidgin/pidgin/work/pidgin-2.10.7/config.log
Error: org.macports.configure for port pidgin returned: configure failure: command execution failed
Please see the log file for port pidgin for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_pidgin/pidgin/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port pidgin failed

[an0nym@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

You do not need to Cc yourself, but should Cc the maintainer of the port so that they can begin looking into the problem. I've assigned the port to him for you now.

I see the log says:

:info:configure checking for tclConfig.sh... no
:info:configure configure: error:
:info:configure Tcl development headers not found.

This suggests you did not install the Xcode command line tools; please do so now; see wiki:ProblemHotlist#tclConfig

However I also find it unexpected that pidgin is looking for the system's Tcl. If it's going to use Tcl at all, it should use MacPorts tcl and declare a dependency on it. Or it should disable the use of Tcl.

[an0nym@…]

Replying to ryandesign@…:

This suggests you did not install the Xcode command line tools; please do so now; see wiki:ProblemHotlist#tclConfig

Thanks, it worked. After updating Xcode and updating everything in Xcode - Preferences - Downloads, I didn't notice it no longer includes Command Line Tools.