Hi @AastaLLL ,
Thank you for following up!
The Nx uses default stock Jetpack installation with all components installed.
The system has the library installed, as it seems to me.
Moreover, given the cmake - > build commands are executed not by docker build .m but from the very same container from bash session the install will suffice. the issue is only observable if the container is built from dockerfile using docker build …
Please noticed that our l4t-base container directly mounts CUDA toolkit from the host to reduce image size.
However, there is no mechanism to mount a volume in building time and cause this issue.
A workaround is to copy the CUDA toolkit into the container manually and delete it after compiling.
...
COPY ./cuda-10.2 /usr/local/cuda-10.2
RUN cd git_src/Open3D/theNded/Open3D && mkdir build && cd build && rm -rf * && cmake -DBUILD_EIGEN3=OFF .. && sudo make -j8
We can generate the cmake file correctly with above Dockerfile:
Step 20/20 : RUN cd git_src/Open3D/theNded/Open3D && mkdir build && cd build && rm -rf * && cmake -DBUILD_EIGEN3=OFF .. && sudo make -j8
---> Running in 4b7516f49eda
...
-- Found CUDA: /usr/local/cuda-10.2 (found version "10.2")
-- Building CUDA enabled
-- The CUDA compiler identification is NVIDIA 10.2.89
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - done
-- Check for working CUDA compiler: /usr/local/cuda-10.2/bin/nvcc - skipped
-- Detecting CUDA compile features
-- Detecting CUDA compile features - done
-- Automatic GPU detection failed. Building for common architectures.
-- Autodetected CUDA architecture(s): 3.5;5.0;3.0;5.2;6.0;6.1;7.0;7.5;7.5+PTX
@AastaLLL Thanks, It seems got through the cmake process creation.
However, further at the build step it seems not able to finish the build process.
[ 32%] Building CXX object src/Open3D/Geometry/CMakeFiles/Geometry.dir/PointCloudCluster.cpp.o
[ 32%] Building CUDA object src/Open3D/Core/CMakeFiles/Core.dir/MemoryManagerCUDA.cu.o
nvcc fatal : A single input file is required for a non-link phase when an outputfile is specified
src/Open3D/Core/CMakeFiles/Core.dir/build.make:172: recipe for target 'src/Open3D/Core/CMakeFiles/Core.dir/MemoryManagerCUDA.cu.o' failed
make[2]: *** [src/Open3D/Core/CMakeFiles/Core.dir/MemoryManagerCUDA.cu.o] Error 1
make[1]: *** [src/Open3D/Core/CMakeFiles/Core.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
CMakeFiles/Makefile2:1099: recipe for target 'src/Open3D/Core/CMakeFiles/Core.dir/all' failed
[ 32%] Building CXX object src/Open3D/Geometry/CMakeFiles/Geometry.dir/PointCloudFactory.cpp.o
[ 32%] Building CXX object src/Open3D/Visualization/CMakeFiles/Visualization.dir/Shader/TextureSimpleShader.cpp.o
[ 32%] Building CXX object src/Open3D/Geometry/CMakeFiles/Geometry.dir/PointCloudSegmentation.cpp.o
[ 32%] Built target Utility
---------
[50%] Building CXX object src/Open3D/Geometry/CMakeFiles/Geometry.dir/VoxelGrid.cpp.o
[ 51%] Building CXX object src/Open3D/Geometry/CMakeFiles/Geometry.dir/VoxelGridFactory.cpp.o
[ 51%] Built target Geometry
Makefile:148: recipe for target 'all' failed
make: *** [all] Error 2
The command '/bin/sh -c cd git_src/Open3D/theNded/Open3D && mkdir build && cd build && rm -rf * && cmake -DBUILD_EIGEN3=OFF .. && sudo make -j8' returned a non-zero code: 2
was you able to complete the build step also at your side testing?
the Dockerfile url in the previous post - is it a placeholder or actually there is a downloadable file? it doen’t seem downloadable.
reference file that I tried
However, I noticed, if to commect the latter line, then container will build;
Once it got build it becomes possible to run it in bash mode, then the execution of eigen patch from makes everything seems to build successfully
another open3d issue that I probably should create a separate topic for
./RunSystem /home/user/o3d/git_src/Open3D/theNded/Open3D/examples/Cuda/ReconstructionSystem/config/intel/test.json
[Open3D INFO] Processing fragment 0 / 0
[Open3D INFO] RGBD Odometry between (0 1)
[Open3D INFO] RGBD Odometry between (1 2)
[Open3D INFO] RGBD Odometry between (2 3)
[Open3D INFO] RGBD Odometry between (3 4)
[Open3D INFO] RGBD Odometry between (4 5)
[Open3D INFO] RGBD Odometry between (5 6)
[Open3D INFO] RGBD Odometry between (6 7)
[Open3D INFO] RGBD Odometry between (7 8)
[Open3D INFO] RGBD Odometry between (8 9)
[Open3D INFO] RGBD Odometry between (9 10)
[Open3D INFO] RGBD Odometry between (10 11)
[Open3D INFO] RGBD Odometry between (11 12)
[Open3D INFO] RGBD Odometry between (12 13)
[Open3D INFO] RGBD Odometry between (13 14)
[Open3D INFO] RGBD Odometry between (14 15)
[Open3D INFO] RGBD Odometry between (15 16)
[Open3D INFO] RGBD Odometry between (16 17)
[Open3D INFO] RGBD Odometry between (17 18)
[Open3D INFO] RGBD Odometry between (18 19)
[Open3D INFO] RGBD Odometry between (19 20)
[Open3D INFO] RGBD Odometry between (20 21)
[Open3D INFO] RGBD Odometry between (21 22)
[Open3D INFO] RGBD Odometry between (22 23)
[Open3D INFO] RGBD Odometry between (23 24)
[Open3D INFO] Active subvolumes in volume: 389
[Open3D INFO] Active subvolumes in volume: 440
[Open3D INFO] Active subvolumes in volume: 460
[Open3D INFO] Active subvolumes in volume: 464
[Open3D INFO] Active subvolumes in volume: 473
[Open3D INFO] Active subvolumes in volume: 474
[Open3D INFO] Active subvolumes in volume: 485
[Open3D INFO] Active subvolumes in volume: 486
[Open3D INFO] Active subvolumes in volume: 500
[Open3D INFO] Active subvolumes in volume: 503
[Open3D INFO] Active subvolumes in volume: 509
[Open3D INFO] Active subvolumes in volume: 510
[Open3D INFO] Active subvolumes in volume: 512
[Open3D INFO] Active subvolumes in volume: 514
[Open3D INFO] Active subvolumes in volume: 515
[Open3D INFO] Active subvolumes in volume: 517
[Open3D INFO] Active subvolumes in volume: 521
[Open3D INFO] Active subvolumes in volume: 523
[Open3D INFO] Active subvolumes in volume: 524
[Open3D INFO] Active subvolumes in volume: 529
[Open3D INFO] Active subvolumes in volume: 530
[Open3D INFO] Active subvolumes in volume: 530
[Open3D INFO] Active subvolumes in volume: 534
[Open3D INFO] Active subvolumes in volume: 536
[Open3D INFO] Active subvolumes in volume: 541
[Open3D INFO] Writing 697 subvolumes.
CUDA error at /home/user/o3d/git_src/Open3D/theNded/Open3D/src/Cuda/Integration/ScalableMeshVolumeCudaKernel.cuh:117 code=701(cudaErrorLaunchOutOfResources) "cudaGetLastError()"
Would you mind to share the latest status with us?
Have you successfully built the library?
The first issue listed in this comment seems related to this topic.
Would you mind to check if there is any similar cmake include command in the open3d first.
The other issue for CUDA error 701 is cudaErrorLaunchOutOfResources.
This is a common problem when compiling a desktop library on Jetson.
The root cause is the resource assignment is too large to deploy on Jetson and leads to this error.
This can be solved by reassigning the CUDA resource properly.
Here is an example for pyTorch for your reference.