Opened 7 years ago

Last modified 6 years ago

#7011 new Bugs

Toolset 'intel-darwin' fails as 'stdarg.h' can not be found

Reported by: vogel@… Owned by: Vladimir Prus
Milestone: To Be Determined Component: build
Version: Boost 1.49.0 Severity: Problem
Keywords: Cc:


Building boost (1.49, and also 1.50 beta) using the 'intel-darwin' toolset currently fails on my system, showing errors such as:

compile.c(33): catastrophic error: cannot open source file "stdarg.h"
  # include <stdarg.h>
compilation aborted for compile.c (code 4)

I use the most recent versions of the required developer programs, ICC 12.1.4 and XCode 4.3.3. This appears to be a specific problem of Apple & Intel in case of 'stdarg.h', and the error can be replicated by compiling any C/C++ source file including that header. The problem is also described in Intel's support forum (

Apparently, the problem can be fixed by adding at least one of the following compiler flags:

-isysroot /Applications/
-gcc-name=gcc-4.2 -gxx-name=g++-4.2

Potentially, a call to xcode-select -print-path may be necessary to obtain the correct path. From my perspective, the first option in combination with xcode-select looks to be the most robust solution.

I am, unfortunately, a novice concerning bjam, and can thus not offer a real fix. I will be happy to help if a test run is required. Thank you for help!

Attachments (1)

intel-darwin.patch (1.7 KB) - added by vogel@… 7 years ago.

Download all attachments as: .zip

Change History (4)

Changed 7 years ago by vogel@…

Attachment: intel-darwin.patch added

comment:1 Changed 7 years ago by vogel@…

Having played around for some time, I have made some very minor (and potentially 'dirty') changes to the build system. Like that, boost can be built and installed again (using ./ --with-toolset=intel-darwin and subsequent ./b2 install). The patch has been created from the trunk/ of the SVN repository.

comment:2 Changed 6 years ago by viboes

Component: Building Boostbuild
Owner: set to Vladimir Prus

comment:3 Changed 6 years ago by vogel@…

The problem may be limited to ICC 12.

Note: See TracTickets for help on using tickets.