Open bergentruckung opened 1 year ago
Those linker errors aren't red flags for any issue I'm familiar with. If you provide reproducer instructions similar to the ubuntu build instructions here I can take a look at what is going wrong.
I see, if it helps to add some additional colour, this is the last portion of the build process (after the message from above).
SUBCOMMAND: # //tensorflow/contrib/image:gen_image_ops_py_wrappers_cc [action 'Linking tensorflow/contrib/image/gen_image_ops_py_wrappers_cc [for host]', conf
iguration: fc79f5a2b8c3ab837b6ff6617f003a26cc0d2bb81faca1c37ceff7494a54f2ff, execution platform: @local_config_platform//:host]
(cd /var/tmp/tf.aSaiDr/.cache/bazel/_bazel_bergentruckung/5c5196772a9ffda2bec0a4e93f813cd8/execroot/org_tensorflow && \
exec env - \
PATH=<redacted> \
PWD=/proc/self/cwd \
external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc @bazel-out/host/bin/tensorflow/contrib/image/gen_image_ops_py_wrappers_cc-2.params)
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 977.812s, Critical Path: 251.56s
INFO: 31971 processes: 15017 internal, 16954 local.
FAILED: Build did NOT complete successfully
A reproducer will be similar to this:
./configure
, followed by running the bazel build
commandsHave you tried a bazel clean --expunge
as well as disabling any bazel caching / ccache options you might use?
Sorry, I missed to respond back here. It's still the same for me, even after running bazel clean --expunge
.
We're trying to build CUDA 12.1 (from HEAD of
r1.15.5+nv23.02
) from source on both RHEL 7 and 8 (3.10.0-1160.88.1 and 4.18.0-425.13.1 kernels respectively), but they both fail towards the end at the same place.CUDNN: 8.8.1.3 NCCL: 2.17.1 bazel: 0.25.3 (and a bunch of others as well) gcc: 12.1.1 (from devtoolset-12) Python: 3.10
Relevant trace:
Please let us know how we can go ahead with the build process here.
Thanks in advance.