-
Notifications
You must be signed in to change notification settings - Fork 74.4k
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
Undefined reference to symbol 'ceil@@GLIBC_2.2.5' at build time #1171
Comments
(You may get more help again from the bazel team on this one ...) |
…_2.2.5'" (#3097) * solve the building issues This is to solve #3070, the solution is inspired from bazelbuild/bazel#934 and #1171 * Update BUILD
undefined reference to symbol 'ceil@@GLIBC_2.2.5' git clone --recursive https://github.com/tensorflow/models.git it still gives: is this a Bazel issue? that's a fairly obscure build system, what should I do? |
@sammoes did you figure this out? EDIT:
|
Thanks @rasmi . Just to add that the file that I needed to edit to fix my problem was here: |
…pu_reorg_fixes Fixes to CI CPU/GPU reorg.
I'm working on compiling Tensorflow from source, using non-standard GCC/etc. installations. Environment info: RHEL 6.7, GCC 5.2.1, Bazel 0.1.5. I'm installing Tensorflow from HEAD (commit f82ad36). I'm using a non-CUDA configuration. I've followed the steps @sethbruder suggests in his comment on bazel#649, including copying the contents of
tools
from bazel intotensorflow/tools/
and intotensorflow/google/protobuf/tools/
. This is possibly related to #332, as I'm getting the same error, but at build time as opposed to API usage.I've tried to set up the relevant paths for my non-standard system resource install using the following settings before invoking bazel:
(there may be some leftover settings; this is adapted from what I used for building bazel in bazel#925)
When I invoke bazel with
${MYBAZEL} build -c opt //tensorflow/tools/pip_package:build_pip_package
I get the following error output:
It seems like I may be missing an "-lm" flag in the invocation to gcc to the protobuf target; I've tried including it in LDFLAGS as shown above, but it doesn't seem to be appearing in the gcc invocation.
The text was updated successfully, but these errors were encountered: