Bazel 0.8.1: Build fails with "Xcode version must be specified to use an Apple CROSSTOOL" on OSX High Sierra #4314

dpursehouse · 2017-12-16T05:28:08Z

This is similar to #3063 but not quite the same so I'm adding a new issue rather than commenting on that one again. CC @c-parsons as you were asking me about it before.

While building gerrit, the build failed due to a 404 on one of the dependency downloads. Then, on subsequent builds it failed with Xcode version must be specified to use an Apple CROSSTOOL. It only succeeds (or rather, fails again but with the expected error) after cleaning.

The initial failure caused by 404 when downloading jgit library (seems to have not propagated on maven central yet):

gerrit $ bazel build gerrit
............
ERROR: /Users/dpursehouse/git/gerrit/lib/jgit/org.eclipse.jgit/BUILD:3:1: no such package '@jgit_lib//jar': failed /usr/bin/python /Users/dpursehouse/git/gerrit/tools/download_file.py -o /private/var/tmp/_bazel_dpursehouse/af01e59a244d19667aa266607f080c5a/external/jgit_lib/jar/org.eclipse.jgit-4.9.2.201712150930-r.jar -u MAVEN_CENTRAL:/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar -v a3a2d1df793245ebfc7322db3c2b9828ee184850 --unsign: Download http://repo1.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar
curl: (22) The requested URL returned error: 404 Not Found
error using curl: Command '['curl', '--proxy-anyauth', '-ksSfLo', '/Users/dpursehouse/.gerritcodereview/buck-cache/downloaded-artifacts/org.eclipse.jgit-4.9.2.201712150930-r.jar-a3a2d1df793245ebfc7322db3c2b9828ee184850', 'http://repo1.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar']' returned non-zero exit status 22
 and referenced by '//lib/jgit/org.eclipse.jgit:jgit'
ERROR: Analysis of target '//:gerrit' failed; build aborted: Loading failed
INFO: Elapsed time: 8.959s
FAILED: Build did NOT complete successfully (68 packages loaded)

Subsequent build fails with Xcode version ... error:

gerrit $ bazel build gerrit
ERROR: /private/var/tmp/_bazel_dpursehouse/af01e59a244d19667aa266607f080c5a/external/local_config_cc/BUILD:50:5: in apple_cc_toolchain rule @local_config_cc//:cc-compiler-darwin_x86_64: Xcode version must be specified to use an Apple CROSSTOOL
ERROR: Analysis of target '//:gerrit' failed; build aborted: Analysis of target '@local_config_cc//:cc-compiler-darwin_x86_64' failed; build aborted
INFO: Elapsed time: 0.399s
FAILED: Build did NOT complete successfully (14 packages loaded)
    currently loading: gerrit-util-http ... (2 packages)

Run it again and see that it still fails with the Xcode error:

gerrit $ bazel build gerrit
ERROR: /private/var/tmp/_bazel_dpursehouse/af01e59a244d19667aa266607f080c5a/external/local_config_cc/BUILD:50:5: in apple_cc_toolchain rule @local_config_cc//:cc-compiler-darwin_x86_64: Xcode version must be specified to use an Apple CROSSTOOL
ERROR: Analysis of target '//:gerrit' failed; build aborted: Analysis of target '@local_config_cc//:cc-compiler-darwin_x86_64' failed; build aborted
INFO: Elapsed time: 0.183s
FAILED: Build did NOT complete successfully (0 packages loaded)
    currently loading: lib/lucene

Clean and try again, then it fails with the original (and expected) error

gerrit $ bazel clean --expunge
INFO: Starting clean (this may take a while). Consider using --expunge_async if the clean takes more than several minutes.
gerrit $ bazel build gerrit
............
ERROR: /Users/dpursehouse/git/gerrit/lib/jgit/org.eclipse.jgit/BUILD:3:1: no such package '@jgit_lib//jar': failed /usr/bin/python /Users/dpursehouse/git/gerrit/tools/download_file.py -o /private/var/tmp/_bazel_dpursehouse/af01e59a244d19667aa266607f080c5a/external/jgit_lib/jar/org.eclipse.jgit-4.9.2.201712150930-r.jar -u MAVEN_CENTRAL:/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar -v a3a2d1df793245ebfc7322db3c2b9828ee184850 --unsign: Download http://repo1.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar
curl: (22) The requested URL returned error: 404 Not Found
error using curl: Command '['curl', '--proxy-anyauth', '-ksSfLo', '/Users/dpursehouse/.gerritcodereview/buck-cache/downloaded-artifacts/org.eclipse.jgit-4.9.2.201712150930-r.jar-a3a2d1df793245ebfc7322db3c2b9828ee184850', 'http://repo1.maven.org/maven2/org/eclipse/jgit/org.eclipse.jgit/4.9.2.201712150930-r/org.eclipse.jgit-4.9.2.201712150930-r.jar']' returned non-zero exit status 22
 and referenced by '//lib/jgit/org.eclipse.jgit:jgit'
ERROR: Analysis of target '//:gerrit' failed; build aborted: Loading failed
INFO: Elapsed time: 8.886s
FAILED: Build did NOT complete successfully (63 packages loaded)

OS: OSX High Sierra 10.13.2

The text was updated successfully, but these errors were encountered:

dpursehouse · 2017-12-16T05:29:36Z

gerrit $ bazel version
Build label: 0.8.1-homebrew
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Dec 5 19:33:07 2017 (1512502387)
Build timestamp: 1512502387
Build timestamp as int: 1512502387

dpursehouse · 2017-12-16T05:30:03Z

gerrit $ java -version
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)

aehlig · 2017-12-18T08:10:48Z

@c-parsons as you apparently asked for it, can you take care of triaging this issue? Thanks.

dpursehouse · 2017-12-18T08:15:13Z

Note that the problem can't be reproduced with the exact steps mentioned above any more because that version of jgit is now available on maven. To induce the error, it should be possible to simply change the version to something else that doesn't exist.

kishankarun · 2017-12-22T10:48:52Z

I am facing the similar issue in windows 7.

I had installed bazel with chocolatey (even i had tried with bazel.exe also)

$ tools/eclipse/project.py

Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
ERROR: build interrupted
INFO: Elapsed time: 56.353s
FAILED: Build did NOT complete successfully (0 packages loaded)

Even bazel build

$ bazel build gerrit
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
ERROR: build interrupted
INFO: Elapsed time: 56.353s
FAILED: Build did NOT complete successfully (0 packages loaded)

$ java -version
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

$ bazel version
Build label: 0.9.0
Build target: bazel-out/x64_windows-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Dec 19 09:32:04 2017 (1513675924)
Build timestamp: 1513675924
Build timestamp as int: 1513675924

davido · 2017-12-22T11:22:33Z

@kishankarun Build of Gerrit Code Review on Windows is bleeding edge and work in progress. It doesn't work yet. I don't think your problem is related to this issue. You may want open a new issue, on Gerrit Code Review issue tracker and not here, as it's not Bazel related (probably).

I guess, that you current problem is workspace-status-command that is per default included and must be overwritten. It would also help, if you try to build a small part of gerrit (basic library) and not the whole world. So try this on Gerrit@HEAD:

  $ bazel build --workspace_status_command=tools/workspace-status.cmd --verbose_failures java/com/google/gerrit/common:server

davidstanke · 2018-01-02T21:14:15Z

+1 - I just got this issue ("Xcode version must be specified to use an Apple CROSSTOOL") on macOS 10.12.6 Sierra, using Bazel 0.9.0 installed via Homebrew. It was fixed via bazel clean --expunge. (For the record, I'm building a very simple Java app, with a single local_repository external dep.)

redis-ml · 2018-03-03T19:16:21Z

FYI: I encountered similar issue recently, which got fixed with:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -license
bazel clean --expunge

Reference: https://stackoverflow.com/questions/45276830/xcode-version-must-be-specified-to-use-an-apple-crosstool

kishankarun · 2018-03-05T16:54:38Z

Thanks, @davido, all

aaaa0441 · 2018-08-31T15:30:57Z

@redisliu thanks for the solution. I am trying to build Angular. You saved my night. 👍

lizebang · 2018-10-25T07:15:39Z

@redisliu thanks a lot, good solution.

gsagula · 2019-06-13T08:05:55Z

@redisliu 👍 🥇

pankajdpatil · 2019-10-20T16:20:40Z

@redisliu 👍 Thanks!

jin · 2020-04-24T13:55:40Z

Instead of bazel clean --expunge, you can use bazel sync --configure to not wipe out the external repositories stored in your Bazel output base.

davido · 2020-04-24T14:02:25Z

Instead of bazel clean --expunge, you can use bazel sync --configure to not wipe out your external repository cache.

Gerrit project adjusted: [1] default location of reporsitory cache to be: ~/.gerritcodereview/bazel-cache/repository. So that I would expect, that saying bazel clean --expunge for gerrit project should preserve repositiory cache.

[1] https://gerrit.googlesource.com/gerrit/+/refs/heads/master/.bazelrc#2

jin · 2020-04-24T14:04:27Z

Gerrit project adjusted: [1] default location of reporsitory cache to be: ~/.gerritcodereview/bazel-cache/repository. So that I would expect, that saying bazel clean --expunge for gerrit project should preserve repositiory cache.

Thanks for pointing it out, sorry I mis-spoke. bazel clean --expunge cleans out the Bazel output_base including the external repositories in it, but does not affect --repository_cache, since that's a directory outside of the output_base.

aehlig assigned c-parsons Dec 18, 2017

hlopko added the category: rules > ObjC / iOS / J2ObjC label Jan 2, 2018

s50600822 mentioned this issue Jan 23, 2019

Too many unrelated "xcode version must be specified" errors #6056

Closed

gurezo mentioned this issue Jul 2, 2019

build error gurezo/ng-bazel-sample#2

Closed

jin closed this as completed Apr 24, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bazel 0.8.1: Build fails with "Xcode version must be specified to use an Apple CROSSTOOL" on OSX High Sierra #4314

Bazel 0.8.1: Build fails with "Xcode version must be specified to use an Apple CROSSTOOL" on OSX High Sierra #4314

dpursehouse commented Dec 16, 2017

dpursehouse commented Dec 16, 2017

dpursehouse commented Dec 16, 2017

aehlig commented Dec 18, 2017

dpursehouse commented Dec 18, 2017

kishankarun commented Dec 22, 2017 •

edited

Loading

davido commented Dec 22, 2017 •

edited

Loading

davidstanke commented Jan 2, 2018

redis-ml commented Mar 3, 2018

kishankarun commented Mar 5, 2018

aaaa0441 commented Aug 31, 2018

lizebang commented Oct 25, 2018

gsagula commented Jun 13, 2019

pankajdpatil commented Oct 20, 2019

jin commented Apr 24, 2020 •

edited

Loading

davido commented Apr 24, 2020

jin commented Apr 24, 2020

Bazel 0.8.1: Build fails with "Xcode version must be specified to use an Apple CROSSTOOL" on OSX High Sierra #4314

Bazel 0.8.1: Build fails with "Xcode version must be specified to use an Apple CROSSTOOL" on OSX High Sierra #4314

Comments

dpursehouse commented Dec 16, 2017

dpursehouse commented Dec 16, 2017

dpursehouse commented Dec 16, 2017

aehlig commented Dec 18, 2017

dpursehouse commented Dec 18, 2017

kishankarun commented Dec 22, 2017 • edited Loading

davido commented Dec 22, 2017 • edited Loading

davidstanke commented Jan 2, 2018

redis-ml commented Mar 3, 2018

kishankarun commented Mar 5, 2018

aaaa0441 commented Aug 31, 2018

lizebang commented Oct 25, 2018

gsagula commented Jun 13, 2019

pankajdpatil commented Oct 20, 2019

jin commented Apr 24, 2020 • edited Loading

davido commented Apr 24, 2020

jin commented Apr 24, 2020

kishankarun commented Dec 22, 2017 •

edited

Loading

davido commented Dec 22, 2017 •

edited

Loading

jin commented Apr 24, 2020 •

edited

Loading