Repository navigation
xcrun error when building master #12531
Description
Activity
- addedbuildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.macosIssues and PRs related to the macOS platform.Issues and PRs related to the macOS platform.
on Apr 20, 2017 The issue with the
xcodebuildwarnings is that onmacOSyou can have either the full Xcode, or just the command line tools (similar to theVisual Studio/Visual C++ build toolson Windows). The command line tools don't includexcodebuild, butgypcalls it and then never uses it so it's not actually a problem. I'm not sure if thexcrunis a similar problem, but looking at the commit diff, it looks likexcrunwas already being called prior to this, it just wasn't giving errors.Reacted by Robin Edwards@gibfahn can you verify it's
tools/gyp/pylib/gyp/mac_tool.py: 79 - args = ['xcrun', 'ibtool', '--errors', '--warnings', '--notices', 80 - '--output-format', 'human-readable-text', '--compile', dest, source] 86 + args = ['xcrun', 'ibtool', '--errors', '--warnings', '--notices']So I can dig deeper?
(I meen that whole patched area )
Is your
os.environ['XCODE_VERSION_ACTUAL'] > '0700'?I put some print statements in there but nothing happened. I don't know enough about GYP to know whether that file is even being triggered. I think it might not be.
I don't have any XCODE things in my environment (or
os.environ) at all.Hmm. I'll have to spin up my hackintosh VM.
Which OSX ver you have? and version of the "Xcode Command Line Tools"?P.S. you say these errors comes from
GYP(i.e../configure) not theninjarun, right?[not a solution]
P.P.S. have you tried https://github.com/nodejs/node-gyp? Mostly as an exercise...- rename
/tools/gyp_node.py- to stopGYPfrom running - run
./configureto generateconfig.gypi - run
gyp.js -Icommon.gypi -Iconfig.gypi [-Dtarget_arch=x64] node.gyp
- rename
macOS 10.12.4 (16E195) (the latest Sierra).
Yes, errors come from
./configure.Not sure how to tell which version of the command line tools, but it should be the latest, here's the output of
clang --version.➜ node git:(master) ✗ ❯ clang --version ~/wrk/com/node Apple LLVM version 8.1.0 (clang-802.0.38) Target: x86_64-apple-darwin16.5.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/binReacted by Refael AckermannAFAIK they are just messages, right? you can
make/ninjaafterwards?10 remaining items
@bnoordhuis making a PR for nodejs/node.
BTW, I was confused because I thought @refack had made a similar patch for upstream gyp, but maybe it didn't land?
It didn't.
- added a commit that references this issue
on Jul 31, 2018 - added 2 commits that reference this issue
on Aug 9, 2018 - added a commit that references this issue
on Oct 20, 2020 - added a commit that references this issue
on Jul 27, 2026
As of I think yesterday, when I run
./configureon macOS, I get a newxcrunerror in addition to thexcodebuildwarnings that we all know and love. The build still passes, but it'd be nice to avoid these.Error: