Tcl related build error on Mac

Development
1

I did a clean build on Mac High Sierra on the latest master and got this build error.

-- tcl: Errors detected - See below.

In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/regcomp.c:33:
In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/regguts.h:36:
In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/regcustom.h:33:
In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/regex.h:4:
In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/tclInt.h:36:
In file included from /Users/cpinter/Devel/S4R/tcl/tcl/generic/tclPort.h:23:
./tclUnixPort.h:32:10: fatal error: 'errno.h' file not found
#include <errno.h>
         ^~~~~~~~~
1 error generated.
make[3]: *** [regcomp.o] Error 1

CMake Error at /Users/cpinter/Devel/Slicer4/CMake/ExternalProjectForNonCMakeProject.cmake:76 (message):
  tcl: Error in build step.  See
  /Users/cpinter/Devel/S4R/tcl_build_step_output.txt and
  /Users/cpinter/Devel/S4R/tcl_build_step_error.txt
Call Stack (most recent call first):
  /Users/cpinter/Devel/S4R/tcl_build_step.cmake:3 (ExternalProject_Execute)

Has anyone seen the same? Do I do anything wrong? Here’s how I configure (has not changed in the past two years other than deployment target):

/Applications/CMake.app/Contents/bin/cmake -DCMAKE_BUILD_TYPE:STRING=Release -DQT_QMAKE_EXECUTABLE:FILEPATH=/usr/local/Cellar/qt/4.8.7_3/bin/qmake -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=10.13 ../Slicer4
2

Did you update Xcode and the command line tools along with High Sierra? errno.h is in /usr/include and is a standard UNIX include file, seems like maybe basic build environment is missing/misconfigured.

3

Thanks for the tip! When I started XCode it did install some components. Unfortunately the error didn’t go away even after a clean build.

4

Hmm. Do you see errno.h in /usr/include? Also, run the App Store and look under Updates, and see if there’s an entry for Command Line Tools. This is supposed to be updated when you update Xcode, but I’ve seen weird things where I had to update command line tools AND Xcode separately.

Did you do a complete blow-away-the-entire-build-directory and re-run CMake from scratch?

5

Thanks for the suggestions, Hollister! I was just able to check these out. There is no usr/include directory at all, so no errno.h either. Yes I did a clean build from scratch. I haven’t found the command line tools in the app store yet, but I keep looking. Do you know what it’s called exactly? Thanks!

6

I just realized that the command-line tools can be installed from the command line :slight_smile: The build is going well so far…