Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't build Bazel using Intel compiler (1) #662

Closed
mj-harvey opened this issue Nov 30, 2015 · 1 comment
Closed

Can't build Bazel using Intel compiler (1) #662

mj-harvey opened this issue Nov 30, 2015 · 1 comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) platform: other type: feature request
Milestone

Comments

@mj-harvey
Copy link

Building Bazel on RHEL 6 using commit c1b1eed

In the absence of any documentation about doing this, I've set the paths for the "gcc" fields found in tools/cpp/CROSSTOOL to the fully-qualified path of icpc. Compiling gives:

'''
$ ./compile.sh
INFO: You can skip this first step by providing a path to the bazel binary as second argument:
INFO: ./compile.sh build /path/to/bazel
🍃 Building Bazel from scratch.....
Compiling client .cc files...
icpc -I. -std=c++0x -c -DBLAZE_JAVA_CPU="k8" -DBLAZE_OPENSOURCE=1 -o /tmp/bazel.VWjj8WH4/objs/numbers.cc.o src/main/cpp/util/numbers.cc
src/main/cpp/util/numbers.cc(110): error: constant value is not known
static_assert(vmax > 0, "");
^

src/main/cpp/util/numbers.cc(140): error: constant value is not known
static_assert(vmin < 0, "");
^

compilation aborted for src/main/cpp/util/numbers.cc (code 2)

'''

$ icpc -v
icpc version 15.0.3 (gcc version 4.4.6 compatibility)

@damienmg damienmg added type: feature request P3 We're not considering working on this, but happy to review a PR. (No assignee) labels Dec 1, 2015
@damienmg damienmg modified the milestone: 1.0 Jun 14, 2016
@davidstanke
Copy link
Contributor

@mj-harvey Is this still relevant? (Can we move all discussion to #664?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) platform: other type: feature request
Projects
None yet
Development

No branches or pull requests

4 participants