Running the sensor on linux


Advanced search

Message boards : Number crunching : Running the sensor on linux

Author Message
Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 418 - Posted: 29 Oct 2011 | 22:04:53 UTC

If you run into problems on Linux and the sensor is not detected -

stderr wrote:
cannot query manufacturer for device: [quote=stderr]error sending control message: Operation not permitted
or
error sending control message: Operation not permitted
- you probably have to add user which runs BOINC to group "plugdev" if your system runs udevd.
On my system the user that runs BOINC is "boinc" so I did the following:

(as root)

usermod -a -G plugdev boinc

You may also need to create an entry in /etc/udev/rules.d
For example, I created a file named 53-radioactive.rules - I don't know if the number means anything, I picked it at random.
Inside the file I put this:

#r@h
SYSFS{idVendor}=="16c0", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"


After the two steps above, udevd restart is required and the sensor should be correctly detected and recognised:

stderr wrote:

Stderr output
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
Radac $Rev: 254 $ starting...
Found sensor v2.01
78942,21,2011-10-29 16:53:37,1,f,0.000000
118495,32,2011-10-29 16:54:16,2,n,0.008264
158049,42,2011-10-29 16:54:56,3,n,0.016529
197604,50,2011-10-29 16:55:36,4,n,0.024793


Profile Saenger
Send message
Joined: 16 Jun 11
Posts: 134
Credit: 397,149
RAC: 145

Message 419 - Posted: 29 Oct 2011 | 23:17:41 UTC

Thanks, it worked with me.
I only had to get around the meaning of "udevd restart is required", seems like a unplug and re-plug in a USB socket is required, at least that is what did the job here.
____________
Gruesse vom Saenger

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 429 - Posted: 30 Oct 2011 | 17:50:51 UTC - in response to Message 419.

Actually it means the "udevd" daemon or whatever it's called has to be restarted. The simplest way is to reboot the machine.

Profile Saenger
Send message
Joined: 16 Jun 11
Posts: 134
Credit: 397,149
RAC: 145

Message 433 - Posted: 30 Oct 2011 | 18:40:15 UTC - in response to Message 429.

Actually it means the "udevd" daemon or whatever it's called has to be restarted. The simplest way is to reboot the machine.

But not if there is a checkpoint-less RNA-XXL running since 60h, and only at 27% through ;)
I first tried to kill the daemon in the system monitor, but that didn't do it.
Simply pulling the plug from the detector and reattaching it worked fine.
____________
Gruesse vom Saenger

Profile krzyszp
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 16 Apr 11
Posts: 379
Credit: 478,254
RAC: 93

Message 434 - Posted: 30 Oct 2011 | 18:44:56 UTC - in response to Message 433.

I don't think that everything is right on your host or on our charts script.
As you probably can see, very often yours chart is empty. I will investigate this (maybe this is our problem on displaying chart)...
____________
Regards,
Krzysztof 'krzyszp' Piszczek
Android Radioactive@Home Map
Android Radioactive@Home Map - donated
My Workplace

Profile Saenger
Send message
Joined: 16 Jun 11
Posts: 134
Credit: 397,149
RAC: 145

Message 436 - Posted: 30 Oct 2011 | 18:52:56 UTC - in response to Message 434.

I don't think that everything is right on your host or on our charts script.
As you probably can see, very often yours chart is empty. I will investigate this (maybe this is our problem on displaying chart)...

The stderr.txt looks fine, the last messages in BOINC are:
So 30 Okt 2011 19:45:02 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:45:05 CET | Radioactive@Home | [sched_op] Starting scheduler request
So 30 Okt 2011 19:45:05 CET | Radioactive@Home | Sending scheduler request: To send trickle-up message.
So 30 Okt 2011 19:45:05 CET | Radioactive@Home | Not reporting or requesting tasks
So 30 Okt 2011 19:45:05 CET | Radioactive@Home | [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs
So 30 Okt 2011 19:45:05 CET | Radioactive@Home | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 GPUs
So 30 Okt 2011 19:45:07 CET | Radioactive@Home | Scheduler request completed
So 30 Okt 2011 19:45:07 CET | Radioactive@Home | [sched_op] Server version 613
So 30 Okt 2011 19:45:07 CET | Radioactive@Home | Project requested delay of 7 seconds
So 30 Okt 2011 19:45:07 CET | Radioactive@Home | [sched_op] Deferring communication for 7 sec
So 30 Okt 2011 19:45:07 CET | Radioactive@Home | [sched_op] Reason: requested by project
So 30 Okt 2011 19:45:42 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:46:21 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:47:01 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:48:21 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:49:00 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:49:40 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:50:20 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:50:59 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:51:39 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed
So 30 Okt 2011 19:52:19 CET | Radioactive@Home | [checkpoint] result sample_85974_0 checkpointed


So it looks quite right here on my side, at least for me ;)
____________
Gruesse vom Saenger

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 452 - Posted: 30 Oct 2011 | 21:44:08 UTC - in response to Message 436.

It was probably just a minor glitch in one of the scripts, should be fixed now.

wintermute_P3DN!
Send message
Joined: 12 Nov 11
Posts: 5
Credit: 130,676
RAC: 0

Message 514 - Posted: 13 Nov 2011 | 12:12:15 UTC - in response to Message 452.

Hi,
since yesterday i managed to put the sensor-pieces together, but i have a problem.
I am using Linux but the stderr-file shows this line:
"Radac $Rev: 254 $ starting...
error finding 'radioactiveathome.org GRS': The specified device was not found"

It seems another error than that obove, no?
dmesg says:

[ 4329.825042] usb 4-5: new low speed USB device number 4 using ohci_hcd
[ 4329.990010] usb 4-5: device descriptor read/64, error -62
[ 4330.256011] usb 4-5: device descriptor read/64, error -62
[ 4330.514011] usb 4-5: new low speed USB device number 5 using ohci_hcd
[ 4330.572013] hub 4-0:1.0: unable to enumerate USB device on port 5
[ 4331.174020] usb 4-5: new low speed USB device number 6 using ohci_hcd
[ 4331.372987] usb 4-5: New USB device found, idVendor=16c0, idProduct=05df
[ 4331.372990] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4331.372993] usb 4-5: Product: radioactiveathome.org GRS
[ 4331.372994] usb 4-5: Manufacturer: obdev.at
[ 4331.386333] generic-usb 0003:16C0:05DF.0005: hiddev0,hidraw1: USB HID v1.01 Device [obdev.at radioactiveathome.org GRS] on usb-0000:00:04.0-5/input0


and lsusb -v:
Bus 004 Device 006: ID 16c0:05df VOTI
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x16c0 VOTI
idProduct 0x05df
bcdDevice 2.01
iManufacturer 1 obdev.at
iProduct 2 radioactiveathome.org GRS
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 50mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 22
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 100
Device Status: 0x0000
(Bus Powered)


Any hints are welcome!

wintermute_P3DN!
Send message
Joined: 12 Nov 11
Posts: 5
Credit: 130,676
RAC: 0

Message 515 - Posted: 13 Nov 2011 | 20:51:15 UTC - in response to Message 514.

I found the problem, SeLinux is not allowing Boinc to use the sensor. After changing to permissive-Mode i got same errors in stderr as TJM.
I've got fixing that with his udev-rule.
I hope it will work now.

Profile [AF>Libristes] cottesloe
Send message
Joined: 7 Jan 12
Posts: 14
Credit: 314,861
RAC: 0

Message 1105 - Posted: 12 May 2012 | 9:25:07 UTC
Last modified: 12 May 2012 | 9:26:20 UTC

Hello all.
I'm running Ubuntu 12.04.
Confronted with the problem of non-recognition sensor (progress bar to zero % all the time), a friend of the Alliance Francophone gave me the solution on our forum => http://forum.boinc-af.org / index.php? topic = 4163.msg313231; topicseen # msg313231
Using the script rad_sensor_ubu.sh, edit the file /etc/udev/rules.d/53.radioactive.rules and must be replaced SYSFS by ATTRS.
For explanation, SYSFS is no longer supported since version 174 udev daemon. You have to use ATTRS instead.
And everything works normally.

Thank you.
Bye
____________

Profile [AF>Libristes] nico8313
Avatar
Send message
Joined: 11 Oct 11
Posts: 3
Credit: 88,420
RAC: 0

Message 1106 - Posted: 12 May 2012 | 14:22:02 UTC

Hi all,

Yes !
Inside in the file put this


#r@h
ATTRS{idVendor}=="16c0", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1399 - Posted: 26 Oct 2012 | 5:41:20 UTC
Last modified: 26 Oct 2012 | 5:42:48 UTC

I tried to attach th sensor to a Centos 5 64 Bit Linux PC and got the message in the
Stderr output

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>

I tried to to the fix above but got an error when I ran the first command

usermod -a -G plugdev boinc

The error was usermod: unknown group plugdev

Is there a fix for "process got signal 11" error

I believe that is something to so with running a 32 bit application on a 64 bit PC ???

I am running the sensor on a Windows 7 PC at the moment but the Linux PC runs 24/7 so would like to run it on that.
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1408 - Posted: 27 Oct 2012 | 1:39:17 UTC - in response to Message 1399.
Last modified: 27 Oct 2012 | 1:42:52 UTC

I tried again in case it was a one of error but it happened again. There is nothing in the error that gives me a clue where to look to fix this error. I have 32 and 64 bit versions of GLIBC 2.5 loaded which is the best I can do for this version of Centos Linux.

I guess that I won't be able to run the sensor on my version of Linux ??

http://radioactiveathome.org/boinc/result.php?resultid=1071423
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1409 - Posted: 27 Oct 2012 | 9:27:58 UTC - in response to Message 1408.
Last modified: 27 Oct 2012 | 9:31:05 UTC

Try to run the app as standalone and see if it will work then. You'll find the executable in the BOINC data dir, or just run a search for "radac_*".

Signal 11 sometimes means permission problems.
In worst case you'll have to build the app from sources and run as anonymous platform.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1412 - Posted: 28 Oct 2012 | 0:50:53 UTC - in response to Message 1409.
Last modified: 28 Oct 2012 | 0:55:32 UTC

I re-attached and the application failed with the same error. When I ran it from the folder I got another error

radioactiveathome.org_boinc]# ./radac_1.69_i686-pc-linux-gnu__nci
FATAL: kernel too old
Segmentation fault
You have new mail in **

I have the most up to date kernel for CENTOS 5. I can try and use the modified kernel from elrepo which is 3.0.46 something and give that a go. I will have to make a image of the system first in case it all goes wrong.
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1413 - Posted: 28 Oct 2012 | 2:19:12 UTC - in response to Message 1412.

No luck after I updated to the elrepo kernel 3.0.46 still got the error

radioactiveathome.org_boinc]# ./radac_1.69_i686-pc-linux-gnu__nci
FATAL: kernel too old
Segmentation fault
You have new mail in **

I guess I will need to keep my Win 7 PC running.
____________

Proud Founder and member of



Have a look at my WebCam

Dagorath
Avatar
Send message
Joined: 4 Jul 11
Posts: 151
Credit: 42,738
RAC: 0

Message 1414 - Posted: 28 Oct 2012 | 5:09:28 UTC - in response to Message 1413.

I guess I will need to keep my Win 7 PC running.


My god somebody help the poor man quick! He's in danger of reverting back to a lemming!!!!

____________

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1415 - Posted: 28 Oct 2012 | 8:56:22 UTC - in response to Message 1414.
Last modified: 28 Oct 2012 | 9:05:27 UTC

I wanted to run it on Linux as that is running 24/7 for my web site. I have started a Linux Oracle VirtualBox (free) on my window 7 PC and moved my server over to that. I now still only have one PC running 24/7 but have the Linux server and the sensor running.

I think the server is slower on the virtual server though ??

http://http:dingo-den.com
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1416 - Posted: 28 Oct 2012 | 9:36:12 UTC - in response to Message 1415.

Are you familiar with compiling the apps from sources ?
I'll try to post a guide, building the app is rather easy.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1417 - Posted: 29 Oct 2012 | 1:23:56 UTC - in response to Message 1416.

No I am not very good at Linux, never compiled before. I would give it a go if you can provide the guide, help if needed. It may help other users if they have the same problem.
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1420 - Posted: 29 Oct 2012 | 9:43:45 UTC - in response to Message 1417.
Last modified: 29 Oct 2012 | 13:53:57 UTC

The worst part will be installing everything that's required to build BOINC API.
I'm uploading a video guide which shows the build process, but that's on a system which already has all dependencies installed.

For sure you'll need build-essentials (not sure what's the package name on CentOS, anyway it contains make, gcc, g++ and other build tools), automake, autoconf, m4, libtool, pkg-config, libmysql + libmysql-dev, libusb++ and libusb++-dev.

Steps to do:
Create a new folder and cd inside.
Download BOINC sources: "git clone git://boinc.berkeley.edu/boinc.git"
After download is done, you have to enter to the "boinc" dir (created by git) and while inside, run "./_autosetup", "./configure --disable-client --disable-manager", "make". It will take a while.

Then go back up to the folder you made earlier and download the app sources.
Download the app sources for example by running "wget http://radioactiveathome.org/boinc/download/sources/radac_1.64_rev440.zip". Unpack the archive, put the "app" directory inside the one you have created. Enter it and type "make".

This is the process done by me on Debian, note that I cheated a lot by using mc.

http://www.youtube.com/watch?v=s9WHL_k3yoA

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1421 - Posted: 29 Oct 2012 | 14:09:34 UTC - in response to Message 1420.

This is what I needed to install on a fresh centos to build the app exactly like on the video above:


yum update
yum install git-all
yum install make
yum install pkgconfig
yum install autoconf
yum install libtool
yum install openssl-devel
yum install mysql-devel
yum install gcc-c++
yum install unzip
yum install wget
yum install libusb
yum install libusb-devel

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1422 - Posted: 29 Oct 2012 | 14:29:00 UTC - in response to Message 1420.
Last modified: 29 Oct 2012 | 14:31:11 UTC

I had a quick look at the video but it is very hard to see what you are typing at the bottom of that application and what is that application ??

I see know that the commands are

After download is done, you have to enter to the "boinc" dir (created by git) and while inside, run "./_autosetup", "./configure --disable-client --disable-manager", "make". It will take a while.

Do I run these individually. I think I have most of those apps loaded on my Linus but I will check as well before I start.

I am off to bed now as it is 01:28AM but will give it a go tomorrow for sure.

Thanks
____________

Proud Founder and member of



Have a look at my WebCam

Dagorath
Avatar
Send message
Joined: 4 Jul 11
Posts: 151
Credit: 42,738
RAC: 0

Message 1423 - Posted: 29 Oct 2012 | 15:58:31 UTC - in response to Message 1422.

I had a quick look at the video but it is very hard to see what you are typing at the bottom of that application and what is that application ??


I'm not sure either

I see know that the commands are

After download is done, you have to enter to the "boinc" dir (created by git) and while inside, run "./_autosetup", "./configure --disable-client --disable-manager", "make". It will take a while.


Do I run these individually. I think I have most of those apps loaded on my Linus but I will check as well before I start.


You may already have those commands installed but if you install the packages in the following list from TJM it will check and install them if you don't have them already. It will install other things you will need too.


yum update
yum install git-all
yum install make
yum install pkgconfig
yum install autoconf
yum install libtool
yum install openssl-devel
yum install mysql-devel
yum install gcc-c++
yum install unzip
yum install wget
yum install libusb
yum install libusb-devel


Then yes, run the commands individually. The fact they are each within their own set of quotes and are separated by commas indicates they can be run individually. When separated by semicolons they are being run consecutively and are typed all on one line simply as a matter of convenience. (Aside: in the past you may have seen commands separated by | which is the pipe symbol which means the output from the first command pipes into (feeds into) the second command. Whenever the pipe symbol is used you must run the commands together exactly as shown else it won't work. You may also have seen commands separated by && or ||. In some of those cases you must run them exactly as shown but not always.)


____________

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1424 - Posted: 29 Oct 2012 | 17:47:12 UTC - in response to Message 1423.

Try to set the youtube video to 720p and fullscreen. It's not super clear but at least everything should be readable. I have no idea why it lost it's original quality after upload.

Weird thing happened to me because I upgraded one of my test virtual machines to centos 5.5 and the BOINC API does not compile anymore. It stops with error I'm unable to resolve, something about missing .a files.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1425 - Posted: 30 Oct 2012 | 1:33:24 UTC - in response to Message 1424.

I am using Centos 5 kernel 2.6.18-308.16.1.el5. I have just started to install a couple of packages that I did not have then will give it a try.


____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1426 - Posted: 30 Oct 2012 | 1:57:45 UTC
Last modified: 30 Oct 2012 | 2:34:25 UTC

All seemed to be going good till I put in the make command and then all I got was errors: I don't know why it says redhat-linux/4.1.2 ?? I think I upgraded from 4.1.2 to 5.

I might just try and start from scratch load CEBTOS 6 and see if that works and I will not have any problems.

/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:928: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:957: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:973: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:988: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1011: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:364: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1051: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1074: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1091: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1115: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1131: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1151: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1178: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1201: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:396: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1243: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1266: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1284: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1302: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1323: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1344: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1368: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1380: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1391: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1401: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1412: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1425: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:637: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:650: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:663: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:165: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1562: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1576: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1606: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1634: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1664: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1692: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1711: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1725: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1753: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1772: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1786: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1815: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1845: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1874: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1906: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:893: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:909: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:941: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:958: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
../lib/str_util.h: In function 'bool ends_with(const std::string&, const std::string&)':
../lib/str_util.h:40: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'size'
../lib/str_util.h:40: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'size'
../lib/str_util.h:41: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'substr'
../lib/str_util.h:41: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'size'
../lib/str_util.h:41: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'size'
../lib/str_util.h: In function 'bool starts_with(const std::string&, const std::string&)':
../lib/str_util.h:51: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'substr'
../lib/str_util.h:51: error: 'const struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'size'
../lib/str_util.h: In function 'void downcase_string(std::string&)':
../lib/str_util.h:59: error: 'struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'begin'
../lib/str_util.h:59: error: 'p' was not declared in this scope
../lib/str_util.h:59: error: 'struct std::basic_string<char, std::char_traits<char>, std::allocator<char> >' has no member named 'end'
../lib/coproc.h: At global scope:
../lib/coproc.h:274: error: 'std::vector' has not been declared
../lib/coproc.h:274: error: expected ',' or '...' before '<' token
../lib/coproc.h:279: error: 'std::vector' has not been declared
../lib/coproc.h:279: error: expected ',' or '...' before '<' token
../lib/coproc.h:327: error: 'std::vector' has not been declared
../lib/coproc.h:327: error: expected ',' or '...' before '<' token
../lib/coproc.h:366: error: 'std::vector' has not been declared
../lib/coproc.h:366: error: expected ',' or '...' before '<' token
../lib/coproc.h:387: error: 'std::vector' has not been declared
../lib/coproc.h:387: error: expected ',' or '...' before '<' token
../lib/coproc.h:394: error: 'std::vector' has not been declared
../lib/coproc.h:394: error: expected ',' or '...' before '<' token
../lib/coproc.h:401: error: 'std::vector' has not been declared
../lib/coproc.h:401: error: expected ',' or '...' before '<' token
../lib/app_ipc.h:108: error: ISO C++ forbids declaration of 'vector' with no type
../lib/app_ipc.h:108: error: invalid use of '::'
../lib/app_ipc.h:108: error: expected ';' before '<' token
../lib/proc_control.h:26: error: 'std::vector' has not been declared
../lib/proc_control.h:26: error: expected ',' or '...' before '<' token
../lib/proc_control.h:27: warning: 'any_process_exists' initialized and declared 'extern'
../lib/proc_control.h:27: error: 'vector' is not a member of 'std'
../lib/proc_control.h:27: error: expected primary-expression before 'int'
../lib/proc_control.h:28: warning: 'kill_all' initialized and declared 'extern'
../lib/proc_control.h:28: error: variable or field 'kill_all' declared void
../lib/proc_control.h:28: error: 'vector' is not a member of 'std'
../lib/proc_control.h:28: error: expected primary-expression before 'int'
../lib/util.h:28: error: 'std::vector' has not been declared
../lib/util.h:28: error: expected ',' or '...' before '<' token
boinc_api.cpp:109: error: 'std::vector' has not been declared
boinc_api.cpp:204: error: expected initializer before '<' token
boinc_api.cpp: In function 'int setup_shared_mem()':
boinc_api.cpp:280: warning: dereferencing type-punned pointer will break strict-aliasing rules
boinc_api.cpp:286: warning: dereferencing type-punned pointer will break strict-aliasing rules
boinc_api.cpp: In constructor 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, const _Alloc&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
boinc_api.cpp:904: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
boinc_api.cpp:921: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
boinc_api.cpp: In function 'void handle_upload_file_status()':
boinc_api.cpp:923: error: 'upload_file_status' was not declared in this scope
boinc_api.cpp: In constructor 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, const _Alloc&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
boinc_api.cpp:1448: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
boinc_api.cpp: In function 'int boinc_upload_status(std::string&)':
boinc_api.cpp:1477: error: 'upload_file_status' was not declared in this scope
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: At global scope:
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In instantiation of 'std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep_base':
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:154: instantiated from 'std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2052: instantiated from 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:900: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:148: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:149: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In instantiation of 'std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep':
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2052: instantiated from 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:900: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:156: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:202: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:528: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:605: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In constructor 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
boinc_api.cpp:900: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2052: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In destructor 'std::basic_string<_CharT, _Traits, _Alloc>::~basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
boinc_api.cpp:900: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:478: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc: In copy constructor 'std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
boinc_api.cpp:921: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:185: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:185: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:185: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:185: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In member function '_Alloc std::basic_string<_CharT, _Traits, _Alloc>::get_allocator() const [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:478: instantiated from 'std::basic_string<_CharT, _Traits, _Alloc>::~basic_string() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:900: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1534: error: return type 'struct std::allocator<char>' is incomplete
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc: In member function 'std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::assign(const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:486: instantiated from 'std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::operator=(const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:921: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.tcc:252: error: '__a' has incomplete type
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h: In member function 'int std::basic_string<_CharT, _Traits, _Alloc>::compare(const std::basic_string<_CharT, _Traits, _Alloc>&) const [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]':
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2139: instantiated from 'bool std::operator==(const std::basic_string<_CharT, _Traits, _Alloc>&, const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:1479: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1926: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1927: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1928: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2139: instantiated from 'bool std::operator==(const std::basic_string<_CharT, _Traits, _Alloc>&, const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]'
boinc_api.cpp:1479: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1928: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1927: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:1926: error: invalid use of undefined type 'struct std::allocator<char>'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stringfwd.h:49: error: declaration of 'struct std::allocator<char>'
make[2]: *** [boinc_api.lo] Error 1
make[2]: Leaving directory `/root/Desktop/compileBOINC/boinc/api'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Desktop/compileBOINC/boinc'
make: *** [all] Error 2
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1427 - Posted: 30 Oct 2012 | 12:04:24 UTC

OK
1. I installed CenTOS 6.3 fresh install
2. I installed the latest updates and the packages in the list
3. I got all the way to the app directory part after unzipping the radac app.
4. I changed to the app folder and ran the "make" command and it ran but there is an error at the bottom.

I am stopping now as I have been on the computer for eight hours today and that is enough.

Any help appresiated.

the folder I created was "compile_folder" and that is where I unzipped the radoc app as you can see

[root@coopers2 compile_folder]# ls
app boinc radac_1.64_rev440.zip
[root@coopers2 compile_folder]# cd app
[root@coopers2 app]# make
gcc -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hiddata.o hiddata.c
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hidtool.o hidtool.cpp
hidtool.cpp: In function ‘int main(int, char**)’:
hidtool.cpp:867: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:933: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:977: warning: deprecated conversion from string constant to ‘char*’
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o xmlParser/xmlParser.o xmlParser/xmlParser.cpp
ln -s `g++ -print-file-name=libstdc++.a`
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -o hidtool hiddata.o hidtool.o xmlParser/xmlParser.o libstdc++.a -pthread \
../boinc/api/libboinc_api.a \
../boinc/lib/libboinc.a \
`libusb-config --prefix`/lib/libusb.a
g++: /usr/lib/libusb.a: No such file or directory
make: *** [hidtool] Error 1
[root@coopers2 app]#


This is what is inside the app folder after the "make"

[root@coopers2 app]# ls
config.h hiddata.h hidtool.o Makefile.windows util.h
filesys.h hiddata.o libstdc++.a sensors.xml version.h
firmware hidsdi.h Makefile str_util.h xmlParser
hiddata.c hidtool.cpp Makefile_armv5tel url.h


____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1428 - Posted: 30 Oct 2012 | 12:24:41 UTC - in response to Message 1427.
Last modified: 30 Oct 2012 | 20:26:55 UTC

Run a search for "libusb.a" then check if the libusb dir in the Makefile is correct. I think it is placed somewhere else in your system, that's why the linker didn't find it.

EDIT: You have to install two additional packages - "glibc-static" and "libusb-static", then edit the makefile and change "$(USBLIBS_DIR)/lib/libusb.a" to "$(USBLIBS_DIR)/lib64/libusb.a" (only if you're running 64bit version).

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1429 - Posted: 31 Oct 2012 | 0:40:47 UTC - in response to Message 1428.

OK deleted the app folder and unzipped the radac_1.64_rev440.zip again and then changed the Makefile to point to the 64 bit library.

When I ran make it only gave the following and stopped:

[root@coopers2 ~]# cd Desktop/compile_folder/app
[root@coopers2 app]# make
gcc -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hiddata.o hiddata.c
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hidtool.o hidtool.cpp
hidtool.cpp: In function ‘int main(int, char**)’:
hidtool.cpp:867: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:933: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:977: warning: deprecated conversion from string constant to ‘char*’
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o xmlParser/xmlParser.o xmlParser/xmlParser.cpp
ln -s `g++ -print-file-name=libstdc++.a`
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -o hidtool hiddata.o hidtool.o xmlParser/xmlParser.o libstdc++.a -pthread \
../boinc/api/libboinc_api.a \
../boinc/lib/libboinc.a \
`libusb-config --prefix`/lib64/libusb.a
/usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x764d): warning: the use of `mktemp' is dangerous, better use `mkstemp'
strip hidtool
[root@coopers2 app]# cd ..
[root@coopers2 compile_folder]# ls
app boinc radac_1.64_rev440.zip


I am not sure the BOINC make ran correctly as the BOINC folder is different to the one that I normally see.

[root@coopers2 compile_folder]# cd boinc
[root@coopers2 boinc]# ls
aclocal.m4 config.h.in Makefile.am
api config.log Makefile.in
apps config.status Makefile.incl
autom4te.cache config.sub missing
_autosetup configure notes
bolt_checkin_notes.txt configure.ac packages
checkin_notes coprocs project_specific_defines.h
checkin_notes_2002 COPYING py
checkin_notes_2003 COPYING.LESSER rboinc
checkin_notes_2004 COPYRIGHT samples
checkin_notes_2005 curl sched
checkin_notes_2006 db set-version
checkin_notes_2007 depcomp stamp-h1
checkin_notes_2008 doc stripchart
checkin_notes_2009 generate_svn_version.sh svn_version.h
checkin_notes_2010 html test
checkin_notes_2011 INSTALL testbase
checkin_notes_samples install-sh todo
client lib TODO_OLD
clientctrl libtool tools
clientgui locale vda
clientscr ltmain.sh version.h
clienttray m4 version.h.in
compile mac_build version.log
config.guess mac_installer win_build
config.h Makefile zip
[root@coopers2 boinc]# vi Makefile
[root@coopers2 boinc]#

What I haven't tried with Centos 6 is to just download the latest BOINC and see if the radoc app works. I will do that now and post here what happens






____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1430 - Posted: 31 Oct 2012 | 0:45:53 UTC - in response to Message 1429.

The log above shows the completed compilation process.
Check the app folder for an executable 'hidtool' it's the main app.
Connect the sensor and try to run it as standalone app, break it after a while and check if there's a "data.bin" and "stderr.txt".

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1431 - Posted: 31 Oct 2012 | 1:10:37 UTC
Last modified: 31 Oct 2012 | 1:12:10 UTC

I tried to download BOINC 7.0.28 which is the latest stable but Centos 6 glibc is too old to run it. I then downloded the next oldest version 6.12.34 but when I run BOINC I get the error:

[root@coopers2 BOINC]# ./boinc -redirectio &
[2] 2496
[root@coopers2 BOINC]# ./boinc: /usr/lib64/libcurl.so.4: no version information available (required by ./boinc)


The libcurl.so.4 is there but I guess BOINC doen't know the version ?? I installed the 32 bit version just in case.



[root@coopers2 BOINC]# find / -name libcurl.so.4
/usr/lib/libcurl.so.4
/usr/lib64/libcurl.so.4


So I think I will just run it on Windows and give Linux a miss unless you have an answer to my previous post.

Thanks
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1432 - Posted: 31 Oct 2012 | 1:19:23 UTC - in response to Message 1430.
Last modified: 31 Oct 2012 | 1:25:29 UTC

OK it seems to be running as it is beeping but how do I "break it after a while and check if there's a "data.bin" and "stderr.txt"." Cnt C ??

OK used Cntl C and stopped it, but it is working as standalone

12:16:55 (2506): Can't open init data file - running in standalone mode
Radac $Rev: 440 $ starting...
sensors.xml: 6 nodes found
Found sensor v2.01
8267590,3629,2012-10-31 1:16:55,513,f,381683167
8307150,3645,2012-10-31 1:17:35,513,n,381683167
8346700,3663,2012-10-31 1:18:14,513,n,381683167
8386230,3679,2012-10-31 1:18:54,513,n,381683167
8425760,3702,2012-10-31 1:19:34,513,n,381683167
8465300,3722,2012-10-31 1:20:13,513,n,381683167
8504830,3742,2012-10-31 1:20:53,513,n,381683167
8544360,3760,2012-10-31 1:21:32,513,n,381683167
8583890,3772,2012-10-31 1:22:12,513,n,381683167
8623440,3784,2012-10-31 1:22:52,513,n,381683167

Still doesn't help without BOINC to run it though.

Thanks for the help hope you can help me with the BOINC problem ??
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1433 - Posted: 31 Oct 2012 | 7:25:24 UTC - in response to Message 1432.
Last modified: 31 Oct 2012 | 8:52:45 UTC

I've tried to run BOINC and got exactly the same error as you.
Then it can't connect to any project.
I'll try to build the client + manager on CentOS 6.2, just have to update my cloud VM again.

EDIT: The following additional packages are needed to build client + manager:


libcurl-devel
freeglut-devel
libXmu-devel
libXi-devel
libjpeg-devel
sqlite-devel
libnotify-devel


Then you'll have to install "wxGTK-devel". It is not in the standard repository, to get it you have to add RPMForge first -> follow this guide http://wiki.centos.org/AdditionalResources/Repositories/RPMForge
After you have the RPMForge added, run "yum install wxGTK-devel".


With all the packages installed, go to the directory where you have the BOINC sources (the same repository that you have already used to build BOINC API for the app).
There you have to run


make clean
./configure
make


Then wait a bit as it takes around 15 minutes on average system. Check output for errors, if there are none, check the boinc/client directory and look for executables: boinc, boinccmd, boinc_client. Then check boinc/clientgui and look for boincmgr.
If you have all the executables, the easiest way to use them is to get the 7.x release from BOINC page, unpack it and replace all the executables with yours.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1434 - Posted: 31 Oct 2012 | 11:31:05 UTC
Last modified: 31 Oct 2012 | 11:35:22 UTC

I lost my virtual Centos 6 tonight. It got corrupted somehow and would not open and I deleted it out of frustration. I was / am very annoyed as I have been working on this for a few days now and must be at least 20 hours work. I was trying to move my web server over there as well not just working on radioactive@home stuff.

Well I will give it away for another while and leave the sensor running on the Win7 PC and I still have my server running on Centos 5 in virtualbox.

Thanks for all your help and sorry I can't continue.

Cheers


Tomorrow is another day and I have a spare Q6600 that I can load Centos 6.3 on so might start all over again tomorrow or the day after :)
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1447 - Posted: 6 Nov 2012 | 8:20:52 UTC

I am trying to get my web page running with the scripts etc in Centos 6. Having problems mainly due to my lack of knowledge. If I was paying someone and they were as slow as I am I would freak :)

I haven't forgotten and will get back into this by Friday I hope.
____________

Proud Founder and member of



Have a look at my WebCam

Dagorath
Avatar
Send message
Joined: 4 Jul 11
Posts: 151
Credit: 42,738
RAC: 0

Message 1456 - Posted: 7 Nov 2012 | 2:44:10 UTC - in response to Message 1447.

If I was paying someone and they were as slow as I am I would freak :)


I fired myself once because I was so slow. Unfortunately I am also stingy so nobody would work for me. Now I'm stuck with me again :-(


____________

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1471 - Posted: 13 Nov 2012 | 2:58:37 UTC
Last modified: 13 Nov 2012 | 3:17:14 UTC

OK I have my Centos 6 Web Server running in VM and added a new Gallery for family Photos.

I think that the creation of Boinc worked as I found all the executables and moved them to a new download of 7.0.28. I have tested it yet though.

EDIT: BOINC works just fine.

I ran into the same problem as before with the Radioactive make. I have installed all the packages on this thread and I have changed the makefile to point to lib64, as I have a 64 bit system, but I still get the following error:

[root@coopers app]# find / -name libusb.a
/usr/lib64/libusb.a

[root@coopers app]# ls
config.h hiddata.c hidtool.cpp Makefile_armv5tel str_util.h version.h
filesys.h hiddata.h Makefile Makefile.windows url.h xmlParser
firmware hidsdi.h Makefile~ sensors.xml util.h

[root@coopers app]# make
gcc -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hiddata.o hiddata.c
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o hidtool.o hidtool.cpp
hidtool.cpp: In function ‘int main(int, char**)’:
hidtool.cpp:867: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:933: warning: deprecated conversion from string constant to ‘char*’
hidtool.cpp:977: warning: deprecated conversion from string constant to ‘char*’
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -c -o xmlParser/xmlParser.o xmlParser/xmlParser.cpp
ln -s `g++ -print-file-name=libstdc++.a`
g++ -O2 -fomit-frame-pointer -fpeel-loops -mtune=i686 -ftree-vectorize -Wl,-O1 -Wl,--as-needed -DAPP_GRAPHICS -I../boinc -I../boinc/lib -I../boinc/api -I. -L. -static -static-libgcc -o hidtool hiddata.o hidtool.o xmlParser/xmlParser.o libstdc++.a -pthread \
../boinc/api/libboinc_api.a \
../boinc/lib/libboinc.a \
`libusb-config --prefix`/lib64/libusb.a
/usr/lib/gcc/x86_64-redhat-linux/4.4.6/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x764d): warning: the use of `mktemp' is dangerous, better use `mkstemp'
strip hidtool


When I look in the app folder the radioactive executable is not there:

[root@coopers app]# ls
config.h hiddata.h hidtool.cpp Makefile~ str_util.h xmlParser
filesys.h hiddata.o hidtool.o Makefile_armv5tel url.h
firmware hidsdi.h libstdc++.a Makefile.windows util.h
hiddata.c hidtool Makefile sensors.xml version.h

Cheers,
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1475 - Posted: 16 Nov 2012 | 16:03:35 UTC - in response to Message 1471.

The executable is there, it is called "hidtool", just rename it.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1481 - Posted: 20 Nov 2012 | 1:23:50 UTC

OK I should have seen that from before. I renamed it to the same name as the one from the project and deleted the project file and use mine nowand works fine.

Thanks for the help.
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1482 - Posted: 20 Nov 2012 | 8:57:55 UTC - in response to Message 1481.

I think that without app_info.xml BOINC client will delete the file sooner or later and/or replace it with standard app. Back it up somewhere just in case. I'll make the app_info for linux if needed.

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1565 - Posted: 7 Jan 2013 | 2:21:14 UTC - in response to Message 1482.
Last modified: 7 Jan 2013 | 2:35:57 UTC

Hi

I have attached the sensor to the Linux pc now and it will stay there as that is on 24/7. It is getting very hot here in Australia, today is 42C so I have all my other PC's turned off except the Linux server..

I thought that I needed an app_info but just realized that I freshly installed radioactivity on the linux PC so I must me using the default application and it seems to be running OK.

This post can be ignored........


Radac $Rev: 490 $ starting...
sensors.xml: 6 nodes found
Found sensor v2.01
238690,96,2013-1-7 2:0:8,513,f,381683167
278220,114,2013-1-7 2:0:48,513,n,381683167
317770,124,2013-1-7 2:1:28,513,n,381683167
357310,142,2013-1-7 2:2:7,513,n,381683167
396830,157,2013-1-7 2:2:47,513,n,381683167
436360,175,2013-1-7 2:3:26,513,n,381683167
475900,188,2013-1-7 2:4:6,513,n,381683167
515430,203,2013-1-7 2:4:46,513,n,381683167
554970,218,2013-1-7 2:5:25,513,n,381683167
594500,239,2013-1-7 2:6:5,513,n,381683167
634030,258,2013-1-7 2:6:44,513,n,381683167
673570,270,2013-1-7 2:7:24,513,n,381683167
713100,286,2013-1-7 2:8:4,513,n,381683167
752630,308,2013-1-7 2:8:43,513,n,381683167
792160,333,2013-1-7 2:9:23,513,n,381683167
831680,348,2013-1-7 2:10:3,513,n,381683167
871220,364,2013-1-7 2:10:42,513,n,381683167
910750,383,2013-1-7 2:11:22,513,n,381683167
950280,407,2013-1-7 2:12:1,513,n,381683167
989810,428,2013-1-7 2:12:41,513,n,381683167
1029340,441,2013-1-7 2:13:21,513,n,381683167
1068880,469,2013-1-7 2:14:0,513,n,381683167
1108410,487,2013-1-7 2:14:40,513,n,381683167
1147940,503,2013-1-7 2:15:19,513,n,381683167
1187470,520,2013-1-7 2:15:59,513,n,381683167
1227010,543,2013-1-7 2:16:39,513,n,381683167
1266530,557,2013-1-7 2:17:18,513,n,381683167
1306060,588,2013-1-7 2:17:58,513,n,381683167
1345590,607,2013-1-7 2:18:38,513,n,381683167
1385130,625,2013-1-7 2:19:17,513,n,381683167
1424650,642,2013-1-7 2:19:57,513,n,381683167
1464190,655,2013-1-7 2:20:36,513,n,381683167
1503720,669,2013-1-7 2:21:16,513,n,381683167
1543260,690,2013-1-7 2:21:56,513,n,381683167
1582790,707,2013-1-7 2:22:35,513,n,381683167
1622320,725,2013-1-7 2:23:15,513,n,381683167
1661850,744,2013-1-7 2:23:55,513,n,381683167
1701370,756,2013-1-7 2:24:34,513,n,381683167
1740900,768,2013-1-7 2:25:14,513,n,381683167
1780430,785,2013-1-7 2:25:53,513,n,381683167
1819960,800,2013-1-7 2:26:33,513,n,381683167
1859480,816,2013-1-7 2:27:13,513,n,381683167
1899000,839,2013-1-7 2:27:52,513,n,381683167
1938530,854,2013-1-7 2:28:32,513,n,381683167
1978060,869,2013-1-7 2:29:11,513,n,381683167
2017580,889,2013-1-7 2:29:51,513,n,381683167
2057110,908,2013-1-7 2:30:31,513,n,381683167
2096640,924,2013-1-7 2:31:10,513,n,381683167
2136170,939,2013-1-7 2:31:50,513,n,381683167
2175700,956,2013-1-7 2:32:29,513,n,381683167
2215230,975,2013-1-7 2:33:9,513,n,381683167
2254760,996,2013-1-7 2:33:49,513,n,381683167
2294290,1011,2013-1-7 2:34:28,513,n,381683167
2333830,1039,2013-1-7 2:35:8,513,n,381683167
____________

Proud Founder and member of



Have a look at my WebCam

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 39
Credit: 202,690
RAC: 134

Message 1566 - Posted: 7 Jan 2013 | 2:21:14 UTC - in response to Message 1482.

Hi

I have attached the sensor to the Linux pc now and it will stay there as that is on 24/7. It is getting very hot here in Australia, today is 42C so I have all my other PC's turned off.

Can you supply me with an app_info and a app_config_xml for this application so that if the software is updated on the project I will still be able to use the one I have till I build a new one.

The app_config.xml is the new format for boinc version 7.0.42 onwards I think and the app_info will not work ???

This is one I use for World Community Grid to run multiple gpu applications on one gpu. http://boinc.berkeley.edu/dev/forum_thread.php?id=8051

<app_config>
<app>
<name>hcc1</name>
<user_friendly_name>Help Conquer Cancer</user_friendly_name>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>0.40</cpu_usage>
</gpu_versions>
</app>
</app_config>

Cheers,

Dingo
____________

Proud Founder and member of



Have a look at my WebCam

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,154,993
RAC: 354

Message 1576 - Posted: 11 Jan 2013 | 23:14:26 UTC - in response to Message 1566.
Last modified: 11 Jan 2013 | 23:15:33 UTC

This is the app_info.xml I use for testing:


<app_info>
<app>
<name>radac</name>
<user_friendly_name>R@H beta test</user_friendly_name>
</app>
<file_info>
<name>radac</name>
<executable/>
</file_info>
<file_info>
<name>sensors.xml</name>
</file_info>
<app_version>
<app_name>radac</app_name>
<version_num>175</version_num>
<file_ref>
<file_name>radac</file_name>
<open_name>radac_1.75_linux_intelx64</open_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>sensors.xml</file_name>
<copy_file/>
</file_ref>
</app_version>
</app_info>


it requires executable named "radac" and sensors.xml.

I think the app_config is optional, the app info alone seems to be working for me.

Dagorath
Avatar
Send message
Joined: 4 Jul 11
Posts: 151
Credit: 42,738
RAC: 0

Message 1637 - Posted: 15 Feb 2013 | 20:53:36 UTC - in response to Message 1105.

Hello all.
I'm running Ubuntu 12.04.
Confronted with the problem of non-recognition sensor (progress bar to zero % all the time), a friend of the Alliance Francophone gave me the solution on our forum => http://forum.boinc-af.org / index.php? topic = 4163.msg313231; topicseen # msg313231
Using the script rad_sensor_ubu.sh, edit the file /etc/udev/rules.d/53.radioactive.rules and must be replaced SYSFS by ATTRS.
For explanation, SYSFS is no longer supported since version 174 udev daemon. You have to use ATTRS instead.
And everything works normally.

Thank you.
Bye


There is some misinformation in the above, I think just a typo probably or perhaps that curious French desire to put an S at the end of words but never pronounce it. Actually you must use ATTR not ATTRS.

Also the OP suggested naming the file 53-radioactive.rules. The quote above suggests 53.radioactive.rules. Note the former uses a - in the name, the latter replaces the dash with a dot. The name seems to be important so I will attempt to explain what I have discovered about it in the hopes of sparing others the grief I just went through. Read carefully because I don't explain this very well.

The 53-radioactive.rules name worked for me on Ubuntu 11.10 but since upgrading to Ubuntu 12.10 it appears the detector will not be recognized on my system if I use that filename. According to /etc/udev/rules.d/README (found on Ubuntu 12.10 but perhaps not other distros/versions) the number in the prefix determines the order in which the various device rules files are applied. Mind that works only if the number is followed by a dash character. If you use a period after the number instead of a dash, as is suggested in the above quote, then the number is ignored and the rules file will be applied last after all other rules files have been applied.

The reason I mention that is because not only did I have to switch to using ATTR instead of ATTRS, I also had to replace the dash (-) with a period (.) to get the bloody thing to work on Ubuntu 12.10. In other words it seems the radioactive.rules must be applied last on Ubuntu 12.10. I dunno for sure, just saying what I found does not work versus what does work, for me, YMMV, might not apply to other distros or versions of Ubuntu.

@Dingo... I think the above likely is not related to your troubles.

____________

Profile [AF>Libristes] cottesloe
Send message
Joined: 7 Jan 12
Posts: 14
Credit: 314,861
RAC: 0

Message 2011 - Posted: 12 Sep 2013 | 12:16:12 UTC - in response to Message 1637.

Hello all.
I'm running Ubuntu 12.04.
Confronted with the problem of non-recognition sensor (progress bar to zero % all the time), a friend of the Alliance Francophone gave me the solution on our forum => http://forum.boinc-af.org / index.php? topic = 4163.msg313231; topicseen # msg313231
Using the script rad_sensor_ubu.sh, edit the file /etc/udev/rules.d/53.radioactive.rules and must be replaced SYSFS by ATTRS.
For explanation, SYSFS is no longer supported since version 174 udev daemon. You have to use ATTRS instead.
And everything works normally.

Thank you.
Bye


There is some misinformation in the above, I think just a typo probably or perhaps that curious French desire to put an S at the end of words but never pronounce it. Actually you must use ATTR not ATTRS.

Also the OP suggested naming the file 53-radioactive.rules. The quote above suggests 53.radioactive.rules. Note the former uses a - in the name, the latter replaces the dash with a dot. The name seems to be important so I will attempt to explain what I have discovered about it in the hopes of sparing others the grief I just went through. Read carefully because I don't explain this very well.

The 53-radioactive.rules name worked for me on Ubuntu 11.10 but since upgrading to Ubuntu 12.10 it appears the detector will not be recognized on my system if I use that filename. According to /etc/udev/rules.d/README (found on Ubuntu 12.10 but perhaps not other distros/versions) the number in the prefix determines the order in which the various device rules files are applied. Mind that works only if the number is followed by a dash character. If you use a period after the number instead of a dash, as is suggested in the above quote, then the number is ignored and the rules file will be applied last after all other rules files have been applied.

The reason I mention that is because not only did I have to switch to using ATTR instead of ATTRS, I also had to replace the dash (-) with a period (.) to get the bloody thing to work on Ubuntu 12.10. In other words it seems the radioactive.rules must be applied last on Ubuntu 12.10. I dunno for sure, just saying what I found does not work versus what does work, for me, YMMV, might not apply to other distros or versions of Ubuntu.

@Dingo... I think the above likely is not related to your troubles.


I'm sorry but I didn't make a mistake.
I checked the rad_sensor_ubu.sh file I use, and it is write "ATTRS".
Perhaps "ATTR" is correct too, I didn't try.
I am not responsible for the French grammar, I'm just using it. And I know where to put an "S" when needed.
____________

Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 2053 - Posted: 9 Oct 2013 | 21:21:03 UTC - in response to Message 2011.


I'm sorry but I didn't make a mistake.
I checked the rad_sensor_ubu.sh file I use, and it is write "ATTRS".
Perhaps "ATTR" is correct too, I didn't try.
I am not responsible for the French grammar, I'm just using it. And I know where to put an "S" when needed.


You should ignore the condescending attitude displayed by that person. He does it all the time all over the place.

The fact is that you are both right. Both ATTR and ATTRS are valid. I did a quick google search and learned a ton about udev rules. Almost enough to get it up and running - the fact I did was all down to the efforts of a teammate.

Vato
Avatar
Send message
Joined: 4 Jun 19
Posts: 1
Credit: 6,419
RAC: 146
Message 3831 - Posted: 5 Jul 2019 | 12:44:05 UTC

I just received latest detector, and using clues from this thread and a little modification, it works fine and easy under Ubuntu 16.04.6 LTS. Nothing difficult here, though the vendor ID has changed to 04d8 on the v3.0.1 detector but that's easy to find with 'lsusb -v', the following to be done as root:

usermod -a -G plugdev boinc
cat > /etc/udev/rules.d/53-radioactive.rules
#r@h
ATTRS{idVendor}=="04d8", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"

I did a reboot after this, to be sure it was all right for the long term.

Hope this is useful to someone.

scole of TSBT
Send message
Joined: 2 Jan 19
Posts: 8
Credit: 9,006
RAC: 151
Message 3832 - Posted: 5 Jul 2019 | 21:08:34 UTC

This is what I used to run it on a raspberry pi, borrowed from instructions to run ASICs on BU. It works for any USB device...

By default the user 'boinc' is not allowed to access the USB devices. To do so we need to change the udev rules (or better add one)

As root (sudo....) create a file in the directory /etc/udev/rules.d/ the filename is 50-group.rules, with the following content...


# /etc/udev/rules.d/50-group.rules
SUBSYSTEM!="usb", GOTO="skip_rule"
ACTION=="add", GROUP="plugdev"
LABEL="skip_rule"

This will add a rule that whenever a usb device is added the group for the device-file is set to 'plugdev'. This group already exists on the RPi and the user 'pi' is already a member of that group.

To activate the rule the 'udev' service needs to be restarted...
sudo service udev restart


Now unplug the usb devices, wait a little bit and replug them in.

Now we need to add the user 'boinc' to the group 'plugdev'...
sudo usermod -a -G plugdev boinc



Post to thread

Message boards : Number crunching : Running the sensor on linux


Main page · Your account · Message boards


Copyright © 2019 BOINC@Poland | Open Science for the future