Even with fun tools like yum, sometimes you have no choice but to build an executable from source on Linux. I found that I had to do this when installing BOINC on CentOS 6.5 due to the fact that the precompiled version of the most recent stable version of BOINC, 7.2.42, was compiled against several libraries that Cent)S 6.5 does not have. So here\u2019s how I got everything up and running\u2026<\/p>\n
<\/p>\n
First, I grabbed the source from Git using the following command:<\/p>\n
[codesyntax lang=”bash” container=”div” blockstate=”expanded”]<\/p>\n
git clone git:\/\/boinc.berkeley.edu\/boinc-v2.git boinc<\/pre>\n[\/codesyntax]<\/p>\n
Then, I got the suggested stable version of the client, 7.2.42, by running this command:<\/p>\n
[codesyntax lang=”bash” container=”div” blockstate=”expanded”]<\/p>\n
git checkout client_release\/7.2\/7.2.42; git status<\/pre>\n[\/codesyntax]<\/p>\n
<\/p>\n
I followed the steps here, but with a couple caveats. First, since I don\u2019t need the GUI manager (I\u2019m managing BOINC from another computer, I ran these commands:<\/p>\n
[codesyntax lang=”bash” container=”div” blockstate=”expanded”]<\/p>\n
.\/_autosetup\r\n.\/configure --disable-server \u2013-disable-manager --enable-client CXXFLAGS=\"-O3 \"\r\nmake<\/pre>\n[\/codesyntax]<\/p>\n
<\/p>\n
The instructions then say to go into the packages\/generic\/sea\/ directory, but you don\u2019t need to do this (and it apparently isn\u2019t supported). When I tried, I kept on getting these errors:<\/p>\n
<\/p>\n
[codesyntax lang=”bash” container=”div” blockstate=”expanded”]<\/p>\n
cp ..\/..\/..\/stage\/\/usr\/local\/bin\/boinc BOINC\/boinc\r\n\r\ncp ..\/..\/..\/stage\/\/usr\/local\/bin\/boincmgr BOINC\/boincmgr\r\n\r\ncp: cannot stat `..\/..\/..\/stage\/\/usr\/local\/bin\/boincmgr': No such file or directory\r\nmake: *** [BOINC\/boincmgr] Error 1<\/pre>\n[\/codesyntax]<\/p>\n
<\/p>\n
Instead, just go into the client directory after that first make and the boinc, boinc_client, and boinccmd executables are all in there ready for use. What now? Well, you can run from there, but instead I installed it elsewhere. I copied the executables files to \/var\/lib\/boinc\/ and used that as my permanent run directory. I also created a boinc user and group and chown-ed that directory and all the files in it. Then, I grabbed a shell script from somewhere (this one is close) and tossed it in the \/etc\/init.d directory, configuring the variables as necessary. Finally, I went to the appropriate rcX.d directories and manually created the symlinks to that file, which is the hard way of just using chkconfig.<\/p>\n
Next time, I\u2019ll write about how I configured rsyslog to send BOINC messages to Splunk.<\/p>\n","protected":false},"excerpt":{"rendered":"
Even with fun tools like yum, sometimes you have no choice but to build an executable from source on Linux. I found that I had to do this when installing BOINC on CentOS 6.5 due to the fact that the precompiled version of the most recent stable version of BOINC, 7.2.42, was compiled against several… Continue reading Building and installing BOINC on CentOS 6.5<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[19],"tags":[246,247,21],"class_list":["post-1026","post","type-post","status-publish","format-standard","hentry","category-tech-2","tag-boinc","tag-centos","tag-linux","entry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t