compiling bazel from source; compile.sh terminates instantaneously #1275
Labels
Comments
|
@damienmg Do you have any idea? |
|
I think it might run using a non bash shell. Can you try adding set -x at the top of compile.sh? |
|
@damienmg This is the output I get after adding set -x and running compile.sh |
|
It's failing when calling javac -version What does |
|
No answer since 18 days, closing. |
|
Hi @damienmg , I am also getting same error, while running ./compile.sh, #which javac #javac -version Could you help me on this.? Pl let me know if you need any further information. Thanks in Advance.! |
|
What does it give you if you add |
|
|
I have also tried with bazel .2.2b and got the below error. cd /opt/bazel-0.2.2b/ Building output/bazel |
|
Looks like you don't have cc1plus, the c++ backend compiler for gcc, installed. What environment are you building on, and can you try re-installing GCC with all of the C++ extensions included? |
|
Hi, The package already installed it seems [root@localhost Desktop]# yum install gcc gcc-c++
|
|
I have tried yum groupinstall 'Development Tools' , After that below error occured. [root@localhost bazel-0.2.2b]# ./compile.sh |
|
This seems to be a related issue: tensorflow/tensorflow#82 Is there a chance you also have multiple installations of GCC, and the crosstool file is pointing to the wrong one? |
|
Hi, I belive i've one GCC installed [root@localhost bazel-0.2.2b]# which gcc And Also path to gcc is mentioned correctly in /tools/cpp/CROSSTOOL tool_path { name: "ar" path: "/usr/bin/ar" } |
|
[root@localhost Desktop]# rpm -qa gcc |
|
anyone who got this issue fixed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to compile bazel from source but when I run ./compile.sh, it terminates right away without giving any error messages:
./compile.sh
INFO: You can skip this first step by providing a path to the bazel binary as second argument:
INFO: ./compile.sh compile /path/to/bazel
🍃 Building Bazel from scratch
I suspected maybe my system was running out of memory, but that wasn't the case. Any suggestions on why compile.sh would terminate right away? or perhaps anyone having the same issue with current build?
The text was updated successfully, but these errors were encountered: