here is a ebuild for the latest release from boinc's homepage, version 6.4.5 Reproducible: Always Steps to Reproduce: 1. download the ebuild 2. download the source code from http://www.4shared.com/file/76863663/8297ecfb/boinc-645tar.html?dirPwdVerified=8e5da412 3. copy the source code to /usr/portage/distfiles 4. copy the ebuild to you local overlay and digest it. 5. unmask the package and update boinc Actual Results: you are running boinc-6.4.5 Expected Results: you are running boinc-6.4.5 I have no idea if cuda support is enabled, I'm trying to figure it out, if I'll manage I'll implement it into the ebuild
Created attachment 175961 [details] boinc 6.4.5 ebuild
ok, after some digging, cuda is built in and will work only on projects that supports it and if you have the libs installed.
Thanks for submitting your version bump. Could you provide a brief summary of any changes you made compared to the earlier ebuild you started from?
(In reply to comment #3) > Thanks for submitting your version bump. Could you provide a brief summary of > any changes you made compared to the earlier ebuild you started from? > the ebuild is the same, the only changes are in the source files, I had to include subdirectories that aren't found in the earlier version's tar files.
The demon boinc doesn't start I made this mistake /etc/init.d/boinc-client start /etc/init.d/boinc-client: line 333: [: too many arguments Starting BOINC client as a daemon:
(In reply to comment #5) > The demon boinc doesn't start I made this mistake > > /etc/init.d/boinc-client start > /etc/init.d/boinc-client: line 333: [: too many arguments > Starting BOINC client as a daemon: > what is the difference between boinc and boinc-client? I'm using boinc without any problem...
No, the new name given to the ebuild startup script boinc.
(In reply to comment #7) > No, the new name given to the ebuild startup script boinc. > ok, so is there a problem or not, kinda lost you over here
Yes there is a problem, boinc does not start and it gives the error that I put above. I am not strong enough to find out why.
here is the problematic line: if [ -z `su $BOINCUSER -c "$cmd"` ]; then I dont know how is the publisher of the script, gentoo dev or boinc dev, I personally have no problems running the service by enabling the boinc (not boinc=client) service. try and see if it works.
I wanted to rebuild the program and now I have this to the compilation. x86_64-pc-linux-gnu-g++: libboinc.a: No such file or directory make[2]: *** [crypt_prog] Erreur 1 make[2]: *** Attente des tâches non terminées.... mv -f .deps/gui_rpc_client_ops.Tpo .deps/gui_rpc_client_ops.Po make[2]: quittant le répertoire « /var/tmp/portage/sci-misc/boinc-6.4.5/work /boinc-6.4.5/lib » make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le répertoire « /var/tmp/portage/sci-misc/boinc-6.4.5/work/boinc-6.4.5 » make: *** [all] Erreur 2
(In reply to comment #11) > I wanted to rebuild the program and now I have this to the compilation. > > x86_64-pc-linux-gnu-g++: libboinc.a: No such file or directory > make[2]: *** [crypt_prog] Erreur 1 > make[2]: *** Attente des tâches non terminées.... > mv -f .deps/gui_rpc_client_ops.Tpo .deps/gui_rpc_client_ops.Po > make[2]: quittant le répertoire « /var/tmp/portage/sci-misc/boinc-6.4.5/work > /boinc-6.4.5/lib » > make[1]: *** [all-recursive] Erreur 1 > make[1]: quittant le répertoire « > /var/tmp/portage/sci-misc/boinc-6.4.5/work/boinc-6.4.5 » > make: *** [all] Erreur 2 > did it compiled for you well before?
(In reply to comment #12) > > > did it compiled for you well before? > No, it has never compiled with your ebuild, I had built by hand but it did not work too.
(In reply to comment #13) > (In reply to comment #12) > > > > > > did it compiled for you well before? > > > > No, it has never compiled with your ebuild, I had built by hand but it did not > work too. > ok, did you tried to compile it by hand? if it crashes, then it isn't the ebuild, which source did you tried?
*** Bug 254303 has been marked as a duplicate of this bug. ***
I found the source with this command svn co http://boinc.berkeley.edu/svn/tags/boinc_core_release_6_4_5
(In reply to comment #16) > I found the source with this command svn co > http://boinc.berkeley.edu/svn/tags/boinc_core_release_6_4_5 > thats where I've got the source from
(In reply to comment #11) Re-emerge with MAKEOPTS="-j1", that should do the trick. @DaggyStyle: maybe you should force MAKEOPTS="-j1" in the ebuild?
(In reply to comment #6) > what is the difference between boinc and boinc-client? I'm using boinc without > any problem... boinc is missing, only boinc-client exists
(In reply to comment #19) > (In reply to comment #6) > > what is the difference between boinc and boinc-client? I'm using boinc without > > any problem... > > boinc is missing, only boinc-client exists > Both the configuration file (/etc/conf.d/boinc) and the init-script (/etc/init.d/boinc) are missing in this ebuild. If you did an upgrade then the files from previous version probably work well enough. If you did a fresh emerge OTOH then your only option is to try to install those by hand ...
(In reply to comment #18) > (In reply to comment #11) > > Re-emerge with MAKEOPTS="-j1", that should do the trick. > > @DaggyStyle: maybe you should force MAKEOPTS="-j1" in the ebuild? > It compile fine now but there is always a problem with the file /etc/init.d/boinc that does not exist and is replaced by /etc/init.d/boinc-client that does not work.
I've haven't limited the numbers of jobs and it compiled well, can it be cpu related? in order to have the scripts, just create a files sub folder in the boinc folder and copy the files boinc.init and boinc.conf from the original portage tree.
(In reply to comment #22) > I've haven't limited the numbers of jobs and it compiled well, can it be cpu > related? According to dmesg: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ stepping 03
(In reply to comment #22) > in order to have the scripts, just create a files sub folder in the boinc > folder and copy the files boinc.init and boinc.conf from the original portage > tree. Thanks, that did the trick.
again. maybe it is cpu related but I really doubt it
(In reply to comment #22) > I've haven't limited the numbers of jobs and it compiled well, can it be cpu > related? > AMD Phenom(tm) 9850 Quad-Core Processor stepping 03
we need more users to try it...
here is some feedback I my humble opinion this ebuild install 2 useless files: /etc/default/boinc-client and /etc/init.d/boinc-client boinc-6.2*.ebuild in the official tree can be of some help. That's all for today. herka
cuda, i have located /usr/lib/libcuda.so coming from package nvidia-drivers but I can not find libcudart requested by boinc. What package provide it? herka
I do not know if the language for programming Cuda Nvidia GPUs is implemented under linux.
(In reply to comment #28) > here is some feedback > I my humble opinion this ebuild install 2 useless files: > /etc/default/boinc-client and /etc/init.d/boinc-client > boinc-6.2*.ebuild in the official tree can be of some help. > > That's all for today. > herka > the ebuild was modified from the one in the tree, these files are coming from the ebuild in the tree
(In reply to comment #30) > I do not know if the language for programming Cuda Nvidia GPUs is implemented > under linux. > according to boinc site it is implemented in the client
(In reply to comment #31) > (In reply to comment #28) > > here is some feedback > > I my humble opinion this ebuild install 2 useless files: > > /etc/default/boinc-client and /etc/init.d/boinc-client > > boinc-6.2*.ebuild in the official tree can be of some help. > > > > That's all for today. > > herka > > > the ebuild was modified from the one in the tree, these files are coming from > the ebuild in the tree > not sure about your hyporthesis and if I may, /etc/init.d/boinc-client is not a gentoo init script and is unable to start the client correctly any way (error "/etc/init.d/boinc-client"), while /etc/init.d/boinc is a good one running perfectly (look at the first line #!/sbin/runscript) herka
(In reply to comment #32) > (In reply to comment #30) > > I do not know if the language for programming Cuda Nvidia GPUs is implemented > > under linux. > > > > according to boinc site it is implemented in the client > Any way, the boinc package do not emerge libcudart library that the boinc client miss, neither do dev-util/nvidia-cuda-profiler, dev-util/nvidia-cuda-sdk, dev-util/nvidia-cuda-toolkit or media-gfx/nvidia-cg-toolkit. On the other hand, libcuda is provided by x11-drivers/nvidia-drivers-177.82 (at least) Is there anyone not having the message "Can't load library libcudart" given by the boinc client ? herka
http://isaac.ssl.berkeley.edu/dev/forum_thread.php?id=3431 the support is in, one needs to have the nvidia-drivers installed. again, all I did was to download the source, repack the right files and modify the original files abit. thats it. boinc-client came with the sources, you can find it in the subfolder scripts, I stand corrected, it did not came from gentoo devs. ok, the question is what flags should I add? VIDEO_CARDS_NVIDIA and cuda?
Created attachment 178900 [details] boinc 6.4.5 ebuild managing cudart libraries IMHO some stuff are still to be done, like gui_rpc_auth.cfg proper managment, boinc-client init script and associated files...
have you tried it with my source tarball?
(In reply to comment #37) > have you tried it with my source tarball? > I used yours.
(In reply to comment #38) > (In reply to comment #37) > > have you tried it with my source tarball? > > > > I used yours. > strange, I noticed that it was based on the 6.2.15 in the tree, when I tried to convert it, it failed.... will try again.
I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". Here's what I did: 1. emerged using boinc-6.4.5.ebuild 2. extracted that tarball manually and copied from sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to /var/lib/boinc/ (there's gotta be better solution right?) 3. added boinc user to video group (this makes sure boinc user has access to /dev/nvidiaX devices) I hope this helps someone.
(In reply to comment #40) > I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". > > Here's what I did: > 1. emerged using boinc-6.4.5.ebuild > 2. extracted that tarball manually and copied from > sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to > /var/lib/boinc/ (there's gotta be better solution right?) > 3. added boinc user to video group (this makes sure boinc user has access to > /dev/nvidiaX devices) > > I hope this helps someone. > actually, I can work with that, question is, does there another package that is in portage and has this file, can you check if nvidia-drivers has this file?
(In reply to comment #41) > (In reply to comment #40) > > I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". > > > > Here's what I did: > > 1. emerged using boinc-6.4.5.ebuild > > 2. extracted that tarball manually and copied from > > sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to > > /var/lib/boinc/ (there's gotta be better solution right?) > > 3. added boinc user to video group (this makes sure boinc user has access to > > /dev/nvidiaX devices) > > > > I hope this helps someone. > > > > actually, I can work with that, question is, does there another package that is > in portage and has this file, can you check if nvidia-drivers has this file? > I already checked nvidia-drivers (180.22) and there isn't that file. Not sure actually what library it is. I mean is it even supposed to come with nvidia-drivers or is it just Boinc's own CUDA related library (which for somereason doesn't get installed)?
(In reply to comment #42) > (In reply to comment #41) > > (In reply to comment #40) > > > I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". > > > > > > Here's what I did: > > > 1. emerged using boinc-6.4.5.ebuild > > > 2. extracted that tarball manually and copied from > > > sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to > > > /var/lib/boinc/ (there's gotta be better solution right?) > > > 3. added boinc user to video group (this makes sure boinc user has access to > > > /dev/nvidiaX devices) > > > > > > I hope this helps someone. > > > > > > > actually, I can work with that, question is, does there another package that is > > in portage and has this file, can you check if nvidia-drivers has this file? > > > > I already checked nvidia-drivers (180.22) and there isn't that file. Not sure > actually what library it is. I mean is it even supposed to come with > nvidia-drivers or is it just Boinc's own CUDA related library (which for > somereason doesn't get installed)? > what about these packages? * dev-util/nvidia-cuda-profiler Available versions: ~1.0 Homepage: http://developer.nvidia.com/cuda Description: NVIDIA CUDA Visual Profiler * dev-util/nvidia-cuda-sdk Available versions: ~2.02.0807.1535 {debug emulation} Homepage: http://developer.nvidia.com/cuda Description: NVIDIA CUDA Software Development Kit * dev-util/nvidia-cuda-toolkit Available versions: ~2.0!s {doc} Homepage: http://developer.nvidia.com/cuda Description: NVIDIA CUDA Toolkit does anyone of them has the same file?
This is pointless wasting of resources: first reduce the tarball as much as possible and patch it directly so the ebuild can stay clean. for starters: http://marenka.sh.cvut.cz/~scarab/generate_tarball.sh
And btw in sci overlay i have prepared boinc-bin which is already in 6.4.5 and 6.5.0 versions.
(In reply to comment #45) > And btw in sci overlay i have prepared boinc-bin which is already in 6.4.5 and > 6.5.0 versions. > did you took a look on my tarball? where will you cut more? the purpose of gentoo is compiling and compiling boinc won't take too much that it needs an bin package...
(In reply to comment #44) <cut> > http://marenka.sh.cvut.cz/~scarab/generate_tarball.sh some comment about your script line13: basename is your friend line60: Due to the fact that you distribute your init scripts and conf files you should also rm client/scripts dir (do not forget to sed the main Makefile) Regarding you ebuilds, a bindist use flag should be great if the ebuild can also manage a "compilable" version. AFAIK, some languages included in boinc are missing. herka
(In reply to comment #46) > (In reply to comment #45) > > And btw in sci overlay i have prepared boinc-bin which is already in 6.4.5 and > > 6.5.0 versions. > > > > did you took a look on my tarball? where will you cut more? > the purpose of gentoo is compiling and compiling boinc won't take too much that > it needs an bin package... > Not yet, I am in progress of making source package. Binary is almost ready, so test and help with that. When i have nice and cleaned up initscript. I will throw myself to creating the source one, it is just matter of the time. I am new to boinc and i have to get custom with it. (be happy it has maintainer :D)
(In reply to comment #47) > (In reply to comment #44) > <cut> > > http://marenka.sh.cvut.cz/~scarab/generate_tarball.sh > > some comment about your script > line13: basename is your friend > line60: Due to the fact that you distribute your init scripts and conf files > you should also rm client/scripts dir (do not forget to sed the main Makefile) > > Regarding you ebuilds, a bindist use flag should be great if the ebuild can > also manage a "compilable" version. AFAIK, some languages included in boinc are > missing. > > herka > I know that script is missing ton of things, it is work in progress (this one is basicly first one which made it somehow working). So i accept any enhancement and features. :] I will add it to Documentation/ folder in sci overlay so anybody can post me patches to that. (which would be highly anticipated if you want source client for boinc asap) NOTE: Don't worry my plans are not to rite source version, binary was just easier and i wanted to show you that i care and i am working at least a bit :]
(In reply to comment #48) > (In reply to comment #46) > > (In reply to comment #45) > > > And btw in sci overlay i have prepared boinc-bin which is already in 6.4.5 and > > > 6.5.0 versions. > > > > > > > did you took a look on my tarball? where will you cut more? > > the purpose of gentoo is compiling and compiling boinc won't take too much that > > it needs an bin package... > > > > Not yet, I am in progress of making source package. > Binary is almost ready, > so test and help with that. When i have nice and cleaned up initscript. I will > throw myself to creating the source one, it is just matter of the time. > I am new to boinc and i have to get custom with it. (be happy it has maintainer > :D) > no disrespect but I don't see anything wrong with original boinc binaries, on the contrary, I trust them more because most distros are using them, moreover, I think that it is the best generic binary that can be found. the source that I made is no to different than the one in the tree, I had to add some directories that was needed in the compilation process. the ebuild is ok, I think that the guy in charge of the boinc ebuild knows more on boinc and on programming than me, I tent to trust his ebuild if they are relevant, moreover, you may want to give and init scripts that you like but that is not the case for everyone, for example, a while back I've suggested to remove the net dependency from the init script, dev refused claiming that net is needed when it comes to users that don't mess with boinc, on my init I have removed this dependency but I won't distribute it due to that same reason. I would recommend you won't too.
> no disrespect but I don't see anything wrong with original boinc binaries, on > the contrary, I trust them more because most distros are using them, moreover, > I think that it is the best generic binary that can be found. That is the reason why i am creating boinc-bin ebuild. > > the source that I made is no to different than the one in the tree, I had to > add some directories that was needed in the compilation process. Yes yes that is why i need to work on it more ;P > > the ebuild is ok, I think that the guy in charge of the boinc ebuild knows more > on boinc and on programming than me, I tent to trust his ebuild if they are > relevant, moreover, you may want to give and init scripts that you like but > that is not the case for everyone, for example, a while back I've suggested to > remove the net dependency from the init script, dev refused claiming that net > is needed when it comes to users that don't mess with boinc, on my init I have > removed this dependency but I won't distribute it due to that same reason. I > would recommend you won't too. > Thanks kind words for me :] finaly somebody appreciate my work :D (althrought mostly messy). NOTE: I am the maintainer of boinc :D so when i say i need update init script, i will have to update init script :D
if you are the driver, then it's your call.
(In reply to comment #43) > (In reply to comment #42) > > (In reply to comment #41) > > > (In reply to comment #40) > > > > I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". > > > > > > > > Here's what I did: > > > > 1. emerged using boinc-6.4.5.ebuild > > > > 2. extracted that tarball manually and copied from > > > > sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to > > > > /var/lib/boinc/ (there's gotta be better solution right?) > > > > 3. added boinc user to video group (this makes sure boinc user has access to > > > > /dev/nvidiaX devices) > > > > > > > > I hope this helps someone. > > > > > > > > > > actually, I can work with that, question is, does there another package that is > > > in portage and has this file, can you check if nvidia-drivers has this file? > > > > > > > I already checked nvidia-drivers (180.22) and there isn't that file. Not sure > > actually what library it is. I mean is it even supposed to come with > > nvidia-drivers or is it just Boinc's own CUDA related library (which for > > somereason doesn't get installed)? > > > > what about these packages? * dev-util/nvidia-cuda-profiler > Available versions: ~1.0 > Homepage: http://developer.nvidia.com/cuda > Description: NVIDIA CUDA Visual Profiler > > * dev-util/nvidia-cuda-sdk > Available versions: ~2.02.0807.1535 {debug emulation} > Homepage: http://developer.nvidia.com/cuda > Description: NVIDIA CUDA Software Development Kit > > * dev-util/nvidia-cuda-toolkit > Available versions: ~2.0!s {doc} > Homepage: http://developer.nvidia.com/cuda > Description: NVIDIA CUDA Toolkit > > does anyone of them has the same file? > Hey, I found that file in dev-util/nvidia-cuda-toolkit-2.1. It installs that file in /opt/cuda/lib/ and Boinc doesn't find it. Then I just made symlink "ln -s /opt/cuda/lib/libcudart.so /var/lib/boinc/libcudart.so" and now it's working again.
(In reply to comment #53) > (In reply to comment #43) > > (In reply to comment #42) > > > (In reply to comment #41) > > > > (In reply to comment #40) > > > > > I just got CUDA to work or atleast Boinc tells me that "CUDA devices found". > > > > > > > > > > Here's what I did: > > > > > 1. emerged using boinc-6.4.5.ebuild > > > > > 2. extracted that tarball manually and copied from > > > > > sourcedir/coprocs/CUDA/posix/x86_64-oc-linux-gnu/libcudart.so to > > > > > /var/lib/boinc/ (there's gotta be better solution right?) > > > > > 3. added boinc user to video group (this makes sure boinc user has access to > > > > > /dev/nvidiaX devices) > > > > > > > > > > I hope this helps someone. > > > > > > > > > > > > > actually, I can work with that, question is, does there another package that is > > > > in portage and has this file, can you check if nvidia-drivers has this file? > > > > > > > > > > I already checked nvidia-drivers (180.22) and there isn't that file. Not sure > > > actually what library it is. I mean is it even supposed to come with > > > nvidia-drivers or is it just Boinc's own CUDA related library (which for > > > somereason doesn't get installed)? > > > > > > > what about these packages? * dev-util/nvidia-cuda-profiler > > Available versions: ~1.0 > > Homepage: http://developer.nvidia.com/cuda > > Description: NVIDIA CUDA Visual Profiler > > > > * dev-util/nvidia-cuda-sdk > > Available versions: ~2.02.0807.1535 {debug emulation} > > Homepage: http://developer.nvidia.com/cuda > > Description: NVIDIA CUDA Software Development Kit > > > > * dev-util/nvidia-cuda-toolkit > > Available versions: ~2.0!s {doc} > > Homepage: http://developer.nvidia.com/cuda > > Description: NVIDIA CUDA Toolkit > > > > does anyone of them has the same file? > > > > Hey, I found that file in dev-util/nvidia-cuda-toolkit-2.1. It installs that > file in /opt/cuda/lib/ and Boinc doesn't find it. Then I just made symlink "ln > -s /opt/cuda/lib/libcudart.so /var/lib/boinc/libcudart.so" and now it's working > again. > excellent, so it is a good idea to add it, the question is, should I update my ebuild or Tomáš will do it?
heck, updated the ebuild, I don't have nvidia gpu so I can't test it, you can and post here information, notice that you need to enable the cuda flag.
Created attachment 179429 [details] same ebuild with addition of cuda support flag
Ok: 1) cuda support added to boinc-bin, really thanks for tracking it down 2) start please testing boinc-bin (cause i have to foolproof the inintscripts) 3) script for generating tarbool is mostly ready, what i need is autotools mage which will autoreconf it (i have never done this by not using autotools eclass so i would screw up): http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=blob;f=Documentation/generate_tarball.sh Then i will be ready to finalise your favorite source ebuild. :]
Ok i have working generator :P Now i will fix up the ebuild itself :] (probably tomorow) http://dev.gentooexperimental.org/~scarabeus/boinc-6.4.5.tar.bz2
Ok I added source boinc ebuild in sci overlay. Please test it and report issues.
I took the ebuild on science overlay, it works very well, thank you very much
what is the address of the overlay? I've checked overlays.gentoo.org/proj/science but it isn't there
(In reply to comment #61) > what is the address of the overlay? > I've checked overlays.gentoo.org/proj/science but it isn't there > It's the overlay science in layman db.
if I'm not mistaken is should be the same one (don't use layman, too much of a hassle to setup)
6.4.5 is in the portage. enjoy :]
(In reply to comment #64) > 6.4.5 is in the portage. enjoy :] > bug #257113 :-(
Had the same cuda library issue on X86_64 with boinc-6.4.5-r1. I resolved the issue by changing "ln -s /opt/cuda/lib/libcudart.so /var/lib/boinc/libcudart.so" to "ln -s /opt/cuda/lib64/libcudart.so /var/lib/boinc/libcudart.so"
(In reply to comment #66) > Had the same cuda library issue on X86_64 with boinc-6.4.5-r1. I resolved the > issue by changing > "ln -s /opt/cuda/lib/libcudart.so /var/lib/boinc/libcudart.so" > to > "ln -s /opt/cuda/lib64/libcudart.so /var/lib/boinc/libcudart.so" > use the one in portage, not this one. it is obsolete.
Yes the official portage ebuild was exactly the one I was using (double checked)...
(In reply to comment #68) > Yes the official portage ebuild was exactly the one I was using (double > checked)... > so open a different bug because it won't get fixed here...
