-
Notifications
You must be signed in to change notification settings - Fork 312
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
8.16 or Commits Fail to Compile on Linux #92
Comments
It compiled on CentOS 7 with Cuda 9.1 for me. Instead of a picture, would it be possible to capture the entire output and put it into a gist? |
Is this what you wanted? https://gist.github.com/joesixpack/83be52a48f464b02168a15d79c53ca98 In the meantime, I was able to put in the neoscrypt hack into 8.15. No idea yet if it works or not. |
Which cuda version, driver version and distro? |
I also got "multiple definition of `ROTL64(unsigned long, unsigned char)'" Ubuntu 16.04.3 64-bit Server Edition with all updates. NVIDIA graphics driver and CUDA 9.1.85-1 from NVIDIA's deb repo (
|
There are no multiple definitions of ROTL64. |
I got similar errors like above (collect2, and multiple ROTL64 definitions). Compiled on Ubuntu 16.4, 64-bit desktop. Neither CUDA 9.1 nor 9.0 succeeded, it's probably some other dependencies. |
Let me guess. You are all not using the build.sh script. By the way, I fixed a small typo in configure.sh |
You are dead right! I used ./autogen.sh, then ./configure.sh, then make. facepalm |
I did use the build.sh script and I got that error. |
No problems compiling now. Guess it was that small typo. |
Same here. I'm using build.sh and still getting multiple definition of `ROTL64(unsigned long, unsigned char)' UPD: Sorry, windows branch compiled ok. all above concerns cuda9 branch. And yeah, i know that i should install a newer driver :) |
Spoke too soon. Compiles on Ubuntu 16.04 LTS but not 17.10. |
I am testing on Ubuntu 16 (history has taught me to never use latest).
The gcc 5.4 in current ubuntu 16.04 doesnt work with cuda 9.1. Might be a hard coded invariant in the headers (nvidia loves to do this, even on windows). It builds, it doesn't work for me but it builds. I am trying to add some unified memory support code for Linux so it is much faster than Windows where Unified memory can't be used and the code spends all it's time run memCpy. |
./ccminer -i21 -a neoscrypt --url=stratum+tcp://neoscrypt.usa.nicehash.com:3341 -u 1PVw8bu Based on pooler cpuminer 2.3.2 and the tpruvot@github fork [2017-12-25 10:31:02] NVML GPU monitoring enabled. So it will build on 16.04, but lyra2v2 and neoscrypt neither work. tpruvot 2.2.3-branch cuda9 does work currently (and has to be built the same way). I an not familiar enough with the code to say what is going on, but this block is screaming for UMA support:
|
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1725848 They went from 5.3 to 5.4, broke the bbuild, wontfix. #justmaintainerthings |
You are still using this wierd source code?
Please try the latest commit from the cuda9 branch. Also, -i 21 ? That's too high for neoscrypt. |
dual titan V :-) I was just testing neoscript for the guy who created the issue. To sum up: I think this persons' issue can be closed, although they will not like the answer. It isn't the code, its the toolchain. |
Updated my rig to ubuntu 17.04 (which might be the current sweet spot for cuda9.1) my configure.sh CUDA_CFLAGS='-lineno --shared --compiler-options "-Wall -fPIC"' Ultimately, people are going to have to learn to use autoconfig themselves versus expecting a guide or wrapper that works for all the toolchain combos. Result: ./ccminer -a neoscrypt --url=stratum+tcp://neoscrypt.usa.nicehash.com:3341 -u .titans -p x Based on pooler cpuminer 2.3.2 and the tpruvot@github fork [2017-12-25 13:10:18] NVML GPU monitoring enabled. unfortunately: Based on pooler cpuminer 2.3.2 and the tpruvot@github fork [2017-12-25 13:17:14] NVML GPU monitoring enabled. |
I think that you have old and new files mixed together. |
I'm using current cuda9 branch. Git status shows I am up to date except for my own modified configure.sh, and I've run make clean. |
Line 217 in ef144cf
cuda9 branch |
Yeah, it should be device_map[thr_id]
|
nvidia linux-ism? |
Nevermind, upgrade killed my driver. Hence, it didnt show up as Titan, fixing locally. |
Would you like to do a little experiment? |
"Graphics Device" showing up for Volta Titans on Linux is a known issue. I added a few lines to my local Lyra2Rev to add default intensity when the card is "too new and awesome". Testing your build now. fyi: thats w/ latest drivers/cuda on linux, fun! |
Maybe I should check for the string "Graphics Device" and assume it's a Titan V :-) |
stratum still fails with my local and your test, this doesnt fix anything, but it makes it clear its working as intended
|
Oh, and I have to change the ifdef |
I am getting connected to the stratum, but still not validating. tpruvot rebuilt on the same chain working.
|
Since it works on Windows, it could be unexpected compiler behaviour or wrong compiler options. |
try the option --no-cpu-verify |
lol, smoking
|
Is it possible to provide a docker image for the different working version ? |
Would you please open a seperate issue for the docker stuff? Bye the way, I'm not a Linux user, so I will have to rely on other people who know more about Linux than me. |
Any error message to share ?
Le 22 janv. 2018 17:33, "Clément Garnier" <[email protected]> a
écrit :
… Is it possible to provide a docker image for the different working version
?
I m not used to build cpp stuff and i m fighting with it :D
I m trying to adapt this one https://github.com/kahiroka/
ccminer-in-docker/blob/master/Dockerfile with your fork but for now it s
not working.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#92 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AQeB2plLo9GkVYucqQb7p1Dizi9Pqz2uks5tNLhXgaJpZM4REzaN>
.
|
Yes, its possible to dock this. I run it that way. It works fine.
The only thing needed is a Dockerfile, which I can add to my tree and ask
klaust to pull.
By using Docker, you can have tpruvot running in a xenial-cuda9 docker and
klaust running in a xenial-cuda9.1 docker on the same underlying base OS
(in my case, Zesty).
It seems under cuda-9.1 on linux, you have to disable cpu verify (which
tpruvot does not have an option for, which is why he's still cuda9).
For anyone who finds this later, no, you cannot use Docker for Windows and
load a Xenial Ubuntu Docker for Mining passed through to host GPU.
NVIDIA/nvidia-docker#428
Most Linux users who mine with KlausT on Linux are hermits who do not share
their work. They run farms and make it work for themselves. I will share.
…On Mon, Jan 22, 2018 at 10:39 AM, sukoshi1507 ***@***.***> wrote:
Any error message to share ?
Le 22 janv. 2018 17:33, "Clément Garnier" ***@***.***> a
écrit :
> Is it possible to provide a docker image for the different working
version
> ?
> I m not used to build cpp stuff and i m fighting with it :D
> I m trying to adapt this one https://github.com/kahiroka/
> ccminer-in-docker/blob/master/Dockerfile with your fork but for now it s
> not working.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#92 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AQeB2plLo9GkVYucqQb7p1Dizi9Pqz2uks5tNLhXgaJpZM4REzaN>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AhKu4DxNH6r4lON7HfDxgjsGUFcJ8dJwks5tNLm6gaJpZM4REzaN>
.
|
Could you publish your dockerfiles ? |
8.15 is fine. What a pity as I wanted the neoscrypt fix.
The text was updated successfully, but these errors were encountered: