You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of I think yesterday, when I run ./configure on macOS, I get a new xcrun error in addition to the xcodebuild warnings that we all know and love. The build still passes, but it'd be nice to avoid these.
Error:
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
xcrun: error: unable to lookup item 'PlatformPath' from command line tools installation
xcrun: error: unable to lookup item 'PlatformPath'in SDK '/'
The issue with the xcodebuild warnings is that on macOS you can have either the full Xcode, or just the command line tools (similar to the Visual Studio / Visual C++ build tools on Windows). The command line tools don't include xcodebuild, but gyp calls it and then never uses it so it's not actually a problem. I'm not sure if the xcrun is a similar problem, but looking at the commit diff, it looks like xcrun was already being called prior to this, it just wasn't giving errors.
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.
Activity
gibfahn commentedon Apr 20, 2017
Looks like change comes from: 3a334b1 which was #12450, so cc @refack.
gibfahn commentedon 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.refack commentedon Apr 20, 2017
@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?
refack commentedon Apr 20, 2017
(I meen that whole patched area )
refack commentedon Apr 20, 2017
Is your
os.environ['XCODE_VERSION_ACTUAL'] > '0700'?gibfahn commentedon Apr 20, 2017
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.refack commentedon Apr 20, 2017
Hmm. I'll have to spin up my hackintosh VM.
Which OSX ver you have? and version of the "Xcode Command Line Tools"?
refack commentedon Apr 20, 2017
P.S. you say these errors comes from
GYP(i.e../configure) not theninjarun, right?refack commentedon Apr 20, 2017
[not a solution]
P.P.S. have you tried https://github.com/nodejs/node-gyp? Mostly as an exercise...
/tools/gyp_node.py- to stopGYPfrom running./configureto generateconfig.gypigyp.js -Icommon.gypi -Iconfig.gypi [-Dtarget_arch=x64] node.gypgibfahn commentedon Apr 21, 2017
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/binrefack commentedon Apr 26, 2017
AFAIK they are just messages, right? you can
make/ninjaafterwards?10 remaining items
ryzokuken commentedon Jun 25, 2018
@bnoordhuis making a PR for nodejs/node.
ryzokuken commentedon Jun 25, 2018
BTW, I was confused because I thought @refack had made a similar patch for upstream gyp, but maybe it didn't land?
bnoordhuis commentedon Jun 25, 2018
It didn't.
tools: patch gyp to avoid xcrun errors
tools: patch gyp to avoid xcrun errors
tools: patch gyp to avoid xcrun errors
tools: patch gyp to avoid xcrun errors
tools: patch gyp to avoid xcrun errors