镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

xcrun error when building master #12531

Description

@gibfahn

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 '/'
  • Version: master
  • Platform: macOS
  • Subsystem: build

Activity

  1. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    macosIssues and PRs related to the macOS platform.
    on Apr 20, 2017
  2. gibfahn commented on Apr 20, 2017

    @gibfahn
    MemberAuthor

    Looks like change comes from: 3a334b1 which was #12450, so cc @refack.

  3. gibfahn commented on Apr 20, 2017

    @gibfahn
    MemberAuthor

    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.

  4. refack commented on Apr 20, 2017

    @refack
    Contributor

    @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?

  5. refack commented on Apr 20, 2017

    @refack
    Contributor

    (I meen that whole patched area )

  6. refack commented on Apr 20, 2017

    @refack
    Contributor

    Is your os.environ['XCODE_VERSION_ACTUAL'] > '0700'?

  7. self-assigned this
    on Apr 20, 2017
  8. gibfahn commented on Apr 20, 2017

    @gibfahn
    MemberAuthor

    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.

  9. refack commented on Apr 20, 2017

    @refack
    Contributor

    Hmm. I'll have to spin up my hackintosh VM.
    Which OSX ver you have? and version of the "Xcode Command Line Tools"?

  10. refack commented on Apr 20, 2017

    @refack
    Contributor

    P.S. you say these errors comes from GYP (i.e. ./configure) not the ninja run, right?

  11. refack commented on Apr 20, 2017

    @refack
    Contributor

    [not a solution]
    P.P.S. have you tried https://github.com/nodejs/node-gyp? Mostly as an exercise...

    1. rename /tools/gyp_node.py - to stop GYP from running
    2. run ./configure to generate config.gypi
    3. run gyp.js -Icommon.gypi -Iconfig.gypi [-Dtarget_arch=x64] node.gyp
  12. gibfahn commented on Apr 21, 2017

    @gibfahn
    MemberAuthor

    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/bin
  13. refack commented on Apr 26, 2017

    @refack
    Contributor

    AFAIK they are just messages, right? you can make/ninja afterwards?

  14. 10 remaining items

  15. ryzokuken commented on Jun 25, 2018

    @ryzokuken
    Contributor

    @bnoordhuis making a PR for nodejs/node.

  16. ryzokuken commented on Jun 25, 2018

    @ryzokuken
    Contributor

    BTW, I was confused because I thought @refack had made a similar patch for upstream gyp, but maybe it didn't land?

  17. bnoordhuis commented on Jun 25, 2018

    @bnoordhuis
    Member

    It didn't.

  18. added a commit that references this issue on Jul 31, 2018
  19. removed their assignment
    on Oct 12, 2018
  20. added a commit that references this issue on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.macosIssues and PRs related to the macOS platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions