After installing yasm i am getting the following error in Ubuntu 12.04

balu@jagali:~/cudapts$ make -f makefile.unix
make: ./osfinder.sh: Command not found
make: ./osfinder.sh: Command not found
make: ./osfinder.sh: Command not found
nvcc -O3 -c -arch=sm_35 -o obj/gpuhash.o gpuhash.cu
make: nvcc: Command not found
make: *** [obj/gpuhash.o] Error 127

2 problems here:

1)  Do a git pull again, I added osfinder

2)  You need to have the nvcc compiler in your path.  It's in path-to-your-cuda-install/bin

Yep, linux, I got the the missing package, now this:
make -f makefile.unix
g++ -c -O2  -pthread -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/root/cudapts/cudapts/src -I/root/cudapts/cudapts/src/obj -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -o obj/main_poolminer.o main_poolminer.cpp
g++ -Wl,-z,relro -Wl,-z,now  -o cudapts  obj/cpuid.o obj/sha512_avx.o obj/sha512_sse4.o obj/sha512.o obj/sph_sha2.o obj/sph_sha2big.o obj/gpuhash.o obj/main_poolminer.o -L/usr/local/cuda-5.5/lib64 -Wl,-Bdynamic -l boost_system -l boost_filesystem -l boost_program_options -l boost_thread -l boost_chrono -Wl,-Bdynamic -l z -l dl -l cudart -l pthread
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: cannot find -lboost_chrono
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
make: *** [cudapts] Error 1

Which linux? if Ubuntu:

apt-get install
libboost-chrono1.48-dev libboost1.48-doc libboost-date-time1.48-dev libboost-filesystem1.48-dev libboost-graph-parallel1.48-dev libboost-graph1.48-dev libboost-iostreams1.48-dev libboost-locale1.48-dev libboost-math1.48-dev libboost-mpi1.48-dev libboost-program-options1.48-dev libboost-python1.48-dev libboost-random1.48-dev libboost-regex1.48-dev libboost-serialization1.48-dev libboost-signals1.48-dev libboost-system1.48-dev libboost-test1.48-dev libboost-thread1.48-dev libboost-timer1.48-dev libboost-wave1.48-dev xsltproc doxygen default-jdk

and also
apt-get install libz-dev 

make -f makefile.unix
In file included from main_poolminer.cpp:15:
main_poolminer.hpp:6:28: error: boost/thread.hpp: No such file or directory

Depending on your flavor of linux (is it linux?):

apt-get install libboost-all-dev
or
yum install boost-devel

Quote from: dga on January 08, 2014, 11:11:10 am

Quote from: ryen123 on January 08, 2014, 10:34:17 am

I managed to compile it but got this error when try to run it.

Initializing.  Device has 965951488 free of 1341325312 total bytes of memory
Could not mmap hugepage, reverting to malloc: Cannot allocate memory

You can ignore that error - it was probably working.   I've committed an update that gets rid of it.  It's just informational (and unimportant) with the way the code works now.

  -Dave

Hi Dave, with that error the miner wasn't working, not doing anything. I made a change in makefile.unix line 142

nvcc -O3 -c -arch=sm_35 -o $@ $<

changed to

nvcc -O3 -c -arch=sm_20 -o $@ $<

Recompiled and now running flawlessly no errors. I just tried my luck with that change to reflect the compute capability of my card. Mine is gtx 570. Getting about 670 c/m.

Ahhhhh!  Thank you - I'm really sorry, I left that in for testing.  Your change was right.  I've updated the makefile to use sm_30 as a default and will add this to the readme for now.

Glad it's working!  That's a great rate from an older card.

I managed to compile it but got this error when try to run it.

Initializing.  Device has 965951488 free of 1341325312 total bytes of memory
Could not mmap hugepage, reverting to malloc: Cannot allocate memory

You can ignore that error - it was probably working.   I've committed an update that gets rid of it.  It's just informational (and unimportant) with the way the code works now.

  -Dave

DGA,
   Around here we don't do "contracts" but operate on the basis of trust and informal/non-binding agreements.  My entire trust with the community and valuation of PTS, AGS, and future in the bitcoin space is on the line and I am very well known.   So that is more of a guarantee than any signed contract, it is in my best interest to do right by everyone I deal with.
 
   It is nice that it is based on ptsminer so does that mean it works with standard pools?

   Post the code and when I hear feedback from those on the forum that it works I will pay you 160 PTS. 

Dan
   

ponder.

Done.

It's on github now.

Quote from: dga on January 07, 2014, 11:53:32 pm

Quote from: bytemaster on January 07, 2014, 10:57:04 pm

Quote from: dga on January 07, 2014, 10:50:15 pm

Quote from: bytemaster on January 07, 2014, 09:45:09 pm

Quote from: dga on January 07, 2014, 11:59:36 am

Let me know what you all think.

  -Dave

Would you release this open source for 100 PTS?

I think it's worth more (but then again, I'd say that.  *grin*), but I want to do the right thing by the community, also (or I'd sell it privately as I suspect the previous people to do this did).  How about half the earlier bounty paid for the non-implementation proof, which would be about 160 PTS at current exchange?

  -Dave

If you produce it open source and at least one other person on this forum is able to compile and replicate your results then I will provide 160 PTS to have this in the open for everyone and maintain a fair playing field.

OK.

What's the right approach for ensuring that we can both trust each other on this one?  You have a verification mechanism by having someone replicate the results, which seems appropriate, but is there a similar surety on my side?

I'll start getting the source ready for a quick release now.  I'll update it over the coming weekend to be easier to build and use.

  -Dave

A first cut release is ready.

I've put all of the code except the .cu file on github to verify that this format for a release meets your expectations.

https://github.com/dave-andersen/cudapts

I've licensed my own parts of the code under Apache2.  Because it's based on ptsminer, the .cpp and .hpp files are covered under whatever copyright they started out as, which seems to be lost in the Mac port that I started with.  But the core important thing is the .cu code, and that's basically free for anyone to do anything with.

  -Dave

Quote from: dga on January 07, 2014, 10:50:15 pm

Quote from: bytemaster on January 07, 2014, 09:45:09 pm

Quote from: dga on January 07, 2014, 11:59:36 am

Let me know what you all think.

  -Dave

Would you release this open source for 100 PTS?

I think it's worth more (but then again, I'd say that.  *grin*), but I want to do the right thing by the community, also (or I'd sell it privately as I suspect the previous people to do this did).  How about half the earlier bounty paid for the non-implementation proof, which would be about 160 PTS at current exchange?

  -Dave

If you produce it open source and at least one other person on this forum is able to compile and replicate your results then I will provide 160 PTS to have this in the open for everyone and maintain a fair playing field.

OK.

What's the right approach for ensuring that we can both trust each other on this one?  You have a verification mechanism by having someone replicate the results, which seems appropriate, but is there a similar surety on my side?

I'll start getting the source ready for a quick release now.  I'll update it over the coming weekend to be easier to build and use.

  -Dave