-
Notifications
You must be signed in to change notification settings - Fork 8
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
execvp: ln: Too many levels of symbolic links #8
Comments
Did you run bootstrap.sh before make? |
Yes, we had run bootstrap.sh
…On Thu, 22 Nov 2018 at 01:48, nadyawilliams ***@***.***> wrote:
Did you run bootstrap.sh before make?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ArH6K86hJx_RXa5It5caMTuet81PxCsgks5uxWfOgaJpZM4YsOpO>
.
|
Go to the top directory where you checked out CUDA roll source from github and do pwd and show me the build log from the last command. What is the top most directory where you start form ? Is this a simlink ? |
Here is the output. The prompt is misleading - the machine has centos 7 installed. Not ubuntu! [root@ubuntu-pharm-404 src]# ls ::: rpm-mkdirs ::: if [ ! -x /state/partition1/site-roll/rocks/src/cuda/src/cuda-modules/../..//SOURCES ]; then mkdir -p /state/partition1/site-roll/rocks/src/cuda/src/cuda-modules/../..//SOURCES; fi |
The top level /export is a symbolic link: export -> state/partition1 |
your errors are unlikely related to the roll itself. Check your file system layout. |
OK - I had three NFS mounted directories in the root directory (one mounted on /apps). I have unmounted these. The build now progresses further, but dies. df -h now gives: /dev/mapper/rocks-root 50G 26G 21G 56% / |
in cuda/src/nvidia-toolkit/version.mk set DISTRO as and rerun make |
Hi,
I am trying to build the cuda roll on a new Rocks 7.0 installation.
Following the instructions, I download the cuda roll and run make
The make process dies with an error regarding symbolic links. build.log is attached
build.log
Any advice appreciated!
David
The text was updated successfully, but these errors were encountered: