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

CentOS 7.2 how to change default compiler (--compiler option) #1699

Closed
jgrzybekIntel opened this issue Aug 29, 2016 · 2 comments
Closed

CentOS 7.2 how to change default compiler (--compiler option) #1699

jgrzybekIntel opened this issue Aug 29, 2016 · 2 comments
Assignees

Comments

@jgrzybekIntel
Copy link

jgrzybekIntel commented Aug 29, 2016

Hi all

I saw #1201 but it didn't help me a lot. I am using bazel3.0 and trying to build tensorflow. Default gcc is 4.8.5. I have installed locally gcc 6.1.0 which I want to use to compile TF. TF should be linked to default glibc. I tried to use --compiler switch but I get some errors about toolchain. These are my logs:

$ bazel build -c opt --compiler=gcc-6.1.0 --verbose_failures 
//tensorflow/tools/pip_package:build_pip_package
Warning: ignoring _JAVA_OPTIONS in environment.
WARNING: Sandboxed execution is not supported on your system and thus hermeticity of actions 
cannot be guaranteed. See http://bazel.io/docs/bazel-user-manual.html#sandboxing for more 
information. You can turn off this warning via --ignore_unsupported_sandboxing.
ERROR: No toolchain found for --cpu='k8' --compiler='gcc-6.1.0'. Valid toolchains are: [
  --cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a',
  --cpu='k8' --compiler='compiler' --glibc='local',
].
INFO: Elapsed time: 0.524s

Before running bazel I set:
CXX to /home/jgrzybek/memcpy_tests/gcc-6.1.0-binary/bin/g++
CC to /home/jgrzybek/memcpy_tests/gcc-6.1.0-binary/bin/gcc
and added /home/jgrzybek/memcpy_tests/gcc-6.1.0-binary/bin/ to my PATH

Any suggestions?

@damienmg
Copy link
Contributor

damienmg commented Oct 5, 2016

This should work out of the box without specifying --compiler. Can you try to do a bazel clean --expunge first?

@damienmg damienmg self-assigned this Oct 5, 2016
@damienmg
Copy link
Contributor

I am closing this bug now (12 days of inactivity). Please ping back if you still have the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants