Today

• 18 min ago

  issue 16 (USB error: could not claim interface -1: Invalid argument) commented on by Adriaan.Kleinhout   -   Solved it! I plugged the IR-device in a usb-port which is integrated in my screen, when I plugged it in different device, it worked! Adriaan

  Solved it! I plugged the IR-device in a usb-port which is integrated in my screen, when I plugged it in different device, it worked! Adriaan
• 59 min ago

  issue 16 (USB error: could not claim interface -1: Invalid argument) reported by Adriaan.Kleinhout   -   What steps will reproduce the problem? 1.sudo s710d -d usb 2. 3. What is the expected output? What do you see instead? expected? seen: usb_set_debug(99) usb_set_debug: Setting debugging level to 99 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Skipping non bus directory devices usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 007 on 005 usb_os_find_devices: Found 002 on 005 usb_os_find_devices: Found 001 on 005 Not enough configurations (0 < 1) error obtaining child information: No route to host usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 002 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 002 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 005/007 Opened device: claiming interface now USB error: could not claim interface -1: Invalid argument unable to open port: Invalid argument What version of the product are you using? On what operating system? s710-0.21 Ubuntu 8.04.3 LTS, kernel version 2.6.24-26-rt Please provide any additional information below. -the device is recognized by lsusb: lsusb Bus 005 Device 007: ID 0da4:0001 Polar Electro OY -The device is a Polar IR Interface USB (http://support.polar.fi/PKBSupport.nsf/OldProduct/IRInterfaceUSB?openForm) -My watch is a Polar S625X Hopefully people are still watching this neat piece of software, which I'd really like to get working on my system too! Greetings, Adriaan

  What steps will reproduce the problem? 1.sudo s710d -d usb 2. 3. What is the expected output? What do you see instead? expected? seen: usb_set_debug(99) usb_set_debug: Setting debugging level to 99 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Skipping non bus directory devices usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 007 on 005 usb_os_find_devices: Found 002 on 005 usb_os_find_devices: Found 001 on 005 Not enough configurations (0 < 1) error obtaining child information: No route to host usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 002 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 002 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 005/007 Opened device: claiming interface now USB error: could not claim interface -1: Invalid argument unable to open port: Invalid argument What version of the product are you using? On what operating system? s710-0.21 Ubuntu 8.04.3 LTS, kernel version 2.6.24-26-rt Please provide any additional information below. -the device is recognized by lsusb: lsusb Bus 005 Device 007: ID 0da4:0001 Polar Electro OY -The device is a Polar IR Interface USB (http://support.polar.fi/PKBSupport.nsf/OldProduct/IRInterfaceUSB?openForm) -My watch is a Polar S625X Hopefully people are still watching this neat piece of software, which I'd really like to get working on my system too! Greetings, Adriaan

Earlier this year

• Sep 25, 2009

  issue 15 (CRC errors - Download not possible anymore) commented on by stefan.saring   -   Now I have a new battery, no CRC errors anymore :-) This issue can get closed...

  Now I have a new battery, no CRC errors anymore :-) This issue can get closed...
• Sep 22, 2009

  issue 15 (CRC errors - Download not possible anymore) commented on by stefan.saring   -   The reason seems to be the battery of the watch. Now it also displays the battery symbol, it must get changed.

  The reason seems to be the battery of the watch. Now it also displays the battery symbol, it must get changed.
• Sep 19, 2009

  issue 15 (CRC errors - Download not possible anymore) reported by stefan.saring   -   Hi, I'm using s710 0.21 on Ubuntu 9.04 with a Polar S725X. The download is done by using the Polar USB IR interface. Until some weeks ago everything works well. For some strange reason there's no exercise download possible anymore, both tools s710d and s710sh will fail with CRC errors. The download process is starting (also on the Polar clock), but it's immediately canceled. Details are below. Thanks in advance, Stefan What steps will reproduce the problem? 1. Start s710sh: "s710sh -d usb" 2. Start download: "get files" What is the expected output? What do you see instead? This is the console output: s710sh> get files Reading [ 0 bytes] [ ] [ 0.0%] CRC failed [id 11, length 1029] get files: Resource temporarily unavailable [error] What version of the product are you using? On what operating system? s710 0.21 on Ubuntu 9.04 Please provide any additional information below. Here's the output when starting "s710sh -d usb" (seems to be OK): eddie@delle:~$ s710sh -d usb usb_set_debug(99) usb_set_debug: Setting debugging level to 99 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 002 usb_os_find_busses: Found 008 usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 001 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_devices: Found 003 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 008 usb_os_find_devices: Found 003 on 007 usb_os_find_devices: Found 001 on 007 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 006 usb_os_find_devices: Found 004 on 001 skipping descriptor 0xFF skipping descriptor 0xB skipped 2 class/vendor specific endpoint descriptors skipped 6 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 8 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 002 on 005 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 005 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 006 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 003 skipped 1 class/vendor specific interface descriptors skipping descriptor 0xFF skipped 1 class/vendor specific endpoint descriptors usb_os_find_devices: Found 003 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 003 usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 007/003 Opened device: claiming interface now Claimed interface: ready to receive data s710sh>

  Hi, I'm using s710 0.21 on Ubuntu 9.04 with a Polar S725X. The download is done by using the Polar USB IR interface. Until some weeks ago everything works well. For some strange reason there's no exercise download possible anymore, both tools s710d and s710sh will fail with CRC errors. The download process is starting (also on the Polar clock), but it's immediately canceled. Details are below. Thanks in advance, Stefan What steps will reproduce the problem? 1. Start s710sh: "s710sh -d usb" 2. Start download: "get files" What is the expected output? What do you see instead? This is the console output: s710sh> get files Reading [ 0 bytes] [ ] [ 0.0%] CRC failed [id 11, length 1029] get files: Resource temporarily unavailable [error] What version of the product are you using? On what operating system? s710 0.21 on Ubuntu 9.04 Please provide any additional information below. Here's the output when starting "s710sh -d usb" (seems to be OK): eddie@delle:~$ s710sh -d usb usb_set_debug(99) usb_set_debug: Setting debugging level to 99 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 002 usb_os_find_busses: Found 008 usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 001 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_devices: Found 003 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 008 usb_os_find_devices: Found 003 on 007 usb_os_find_devices: Found 001 on 007 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 006 usb_os_find_devices: Found 004 on 001 skipping descriptor 0xFF skipping descriptor 0xB skipped 2 class/vendor specific endpoint descriptors skipped 6 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 8 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 002 on 005 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 005 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 006 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 003 skipped 1 class/vendor specific interface descriptors skipping descriptor 0xFF skipped 1 class/vendor specific endpoint descriptors usb_os_find_devices: Found 003 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 003 usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 007/003 Opened device: claiming interface now Claimed interface: ready to receive data s710sh>
• Aug 29, 2009

  issue 14 (s710d -d usb will not initialize) reported by thane.poore   -   What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? S710-0.21 Polar S710 wrist unit I have both the sigmatel STIr4210 and the Polar Electro OY Interface Ubuntu 9.04 amd64 Please provide any additional information below. My last steps have been to: - install libusb-devel to get gdlib.config working - create the file /etc/ld.so.conf.d/local.conf and put the following line in it: /usr/local/lib -run ldconfig -thane@thane-desktop:~$ lsusb Bus 001 Device 006: ID 066f:4210 SigmaTel, Inc. STIr4210 IrDA Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0da4:0001 Polar Electro OY Interface Bus 002 Device 003: ID 03f0:0604 Hewlett-Packard DeskJet 840c Bus 002 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub thane@thane-desktop:~$ sudo s710d -d usb s710d[7203]: started s710d[7203]: failed to initialize, aborting I'm afraid at this point I'm stumped. Both of the irda units I received from Polar seem to be inoperable.

  What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? S710-0.21 Polar S710 wrist unit I have both the sigmatel STIr4210 and the Polar Electro OY Interface Ubuntu 9.04 amd64 Please provide any additional information below. My last steps have been to: - install libusb-devel to get gdlib.config working - create the file /etc/ld.so.conf.d/local.conf and put the following line in it: /usr/local/lib -run ldconfig -thane@thane-desktop:~$ lsusb Bus 001 Device 006: ID 066f:4210 SigmaTel, Inc. STIr4210 IrDA Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0da4:0001 Polar Electro OY Interface Bus 002 Device 003: ID 03f0:0604 Hewlett-Packard DeskJet 840c Bus 002 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub thane@thane-desktop:~$ sudo s710d -d usb s710d[7203]: started s710d[7203]: failed to initialize, aborting I'm afraid at this point I'm stumped. Both of the irda units I received from Polar seem to be inoperable.
• Jul 04, 2009

  issue 13 (s710d failed to initialize OpenSuse 11.1 64bit) reported by viebke.schroeder   -   What steps will reproduce the problem? 1. s710d -d usb 2. 3. What is the expected output? What do you see instead? Espected: Running s710d (haven't got there yet so i don't know how that looks like ;)) Instead: s710d[1082]: started s710d[1082]: failed to initialize, aborting What version of the product are you using? On what operating system? OpenSuse11.1 64 bit (2.6.27.23-0.1-trace #1 SMP 2009-05-26 17:02:05 -0400 x86_64 x86_64 x86_64 GNU/Linux ), s710d-0-21 Please provide any additional information below. I tried also with installing libusb and libusb-devel (1-5, 1-0 1-4 installed before) lsusb shows the Flowlink-device that I am using: Bus 003 Device 004: ID 0da4:0003 Polar Electro OY

  What steps will reproduce the problem? 1. s710d -d usb 2. 3. What is the expected output? What do you see instead? Espected: Running s710d (haven't got there yet so i don't know how that looks like ;)) Instead: s710d[1082]: started s710d[1082]: failed to initialize, aborting What version of the product are you using? On what operating system? OpenSuse11.1 64 bit (2.6.27.23-0.1-trace #1 SMP 2009-05-26 17:02:05 -0400 x86_64 x86_64 x86_64 GNU/Linux ), s710d-0-21 Please provide any additional information below. I tried also with installing libusb and libusb-devel (1-5, 1-0 1-4 installed before) lsusb shows the Flowlink-device that I am using: Bus 003 Device 004: ID 0da4:0003 Polar Electro OY
• Jun 24, 2009

  issue 11 (s710d[4250]: failed to initialize, aborting ) commented on by jonathan.harding   -   Resolved

  Resolved
• Jun 24, 2009

  issue 12 (s710 with Ubuntu Linux 9.04) reported by jonathan.harding   -   What steps will reproduce the problem? 1.Compile from Source 2. sudo s710 -d usb What do you see? ... error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 001/021 Opened device: claiming interface now Check that you have permissions to write to 001/021 and, if you don't, that you set up hotplug (http://linux-hotplug.sourceforge.net/) correctly. USB error: could not claim interface 0: Device or resource busy s710d[27330]: failed to initialize, aborting ... What version of the product are you using? On what operating system? Latest Please provide any additional information below.

  What steps will reproduce the problem? 1.Compile from Source 2. sudo s710 -d usb What do you see? ... error obtaining child information: Inappropriate ioctl for device usb_find_devices is done Found Polar USB interface [Vendor 0da4, ProdID 0001] on 001/021 Opened device: claiming interface now Check that you have permissions to write to 001/021 and, if you don't, that you set up hotplug (http://linux-hotplug.sourceforge.net/) correctly. USB error: could not claim interface 0: Device or resource busy s710d[27330]: failed to initialize, aborting ... What version of the product are you using? On what operating system? Latest Please provide any additional information below.
• Jan 23, 2009

  issue 8 (Configure misses libpng when it's present.) commented on by kay.ohnmeiss   -   you need to install libpng-dev and in case of gd.h missing you need to install libgd-dev

  you need to install libpng-dev and in case of gd.h missing you need to install libgd-dev
• Jan 17, 2009

  issue 4 (s710 does not seem to work with new polar USB dongle) commented on by jdjoubert   -   I am running Ubuntu 8.10 and I'm trying to download files from my Polar S725X using a SigmaTel 4200 USB IrDA dongle. I'm getting very much the same behavior (get files: No response) as in comment 11 (http://code.google.com/p/s710/issues/detail?id=4#c11). Can anybody tell me how to resolve this? I haven't applied any patches yet - wanted to find out if someone has got this working?

  I am running Ubuntu 8.10 and I'm trying to download files from my Polar S725X using a SigmaTel 4200 USB IrDA dongle. I'm getting very much the same behavior (get files: No response) as in comment 11 (http://code.google.com/p/s710/issues/detail?id=4#c11). Can anybody tell me how to resolve this? I haven't applied any patches yet - wanted to find out if someone has got this working?
• Jan 05, 2009

  issue 11 (s710d[4250]: failed to initialize, aborting ) reported by jonathan.harding   -   Fedora 8 x86_64 What steps will reproduce the problem? 1. Be a bonehead 2. s710d -d usb 3. Profit? What is the expected output? Found Polar USB interface [Vendor 0da4, ProdID 0001] on 002/035 Opened device: claiming interface now Claimed interface: ready to receive data What do you see instead? s710d[4250]: failed to initialize, aborting What version of the product are you using? On what operating system? .21 Fedora 8 x86_64 Please provide any additional information below. I fixed the problem by install libusb and paying more attention with the output of ./configure. After I install libusb-devel it worked!

  Fedora 8 x86_64 What steps will reproduce the problem? 1. Be a bonehead 2. s710d -d usb 3. Profit? What is the expected output? Found Polar USB interface [Vendor 0da4, ProdID 0001] on 002/035 Opened device: claiming interface now Claimed interface: ready to receive data What do you see instead? s710d[4250]: failed to initialize, aborting What version of the product are you using? On what operating system? .21 Fedora 8 x86_64 Please provide any additional information below. I fixed the problem by install libusb and paying more attention with the output of ./configure. After I install libusb-devel it worked!

Older

• Nov 26, 2008

  issue 4 (s710 does not seem to work with new polar USB dongle) commented on by timhfl   -   I think I have the right file - I will attach if it will allow me to attach.

  I think I have the right file - I will attach if it will allow me to attach.
• Nov 12, 2008

  issue 4 (s710 does not seem to work with new polar USB dongle) commented on by jakommo   -   Hi, does someone still have the stir4210_4220_4116_patch_files.tar.gz file? I have an usb IrDA dongle and I'm searching this patch for days now, the sigmatel website is down because they where sold to freesacle and I can't find the patch anyware else. If someone still got the file please mail me at jakommo at gmail dot com. Thanks jakommo

  Hi, does someone still have the stir4210_4220_4116_patch_files.tar.gz file? I have an usb IrDA dongle and I'm searching this patch for days now, the sigmatel website is down because they where sold to freesacle and I can't find the patch anyware else. If someone still got the file please mail me at jakommo at gmail dot com. Thanks jakommo
• Oct 16, 2008

  issue 10 (Wrong sample - right summery data in human readable output) commented on by i...@christoph-leiter.de   -   OK folks, comparing PolarViewer of Stefan Saring with the s710 sources showed, that the S725 header ist 120 bytes(right) long. So in a first step to get right sample date of a S725 you should edit s710-0.21/include/s710.h Change the following line #define S710_HEADER_SIZES710 109 to #define S710_HEADER_SIZES710 120 The resulting hrm Files can be used with the original Polar Software. Thanks to Dirk Domschowski who explained the basics an found the solution. As the s710 scripts deal with a header size of 109 for the S710 watch some header information gets lost. Actually I don't mind, but as soon as I find some time, I'll hhave a look. Regards, Chris To

  OK folks, comparing PolarViewer of Stefan Saring with the s710 sources showed, that the S725 header ist 120 bytes(right) long. So in a first step to get right sample date of a S725 you should edit s710-0.21/include/s710.h Change the following line #define S710_HEADER_SIZES710 109 to #define S710_HEADER_SIZES710 120 The resulting hrm Files can be used with the original Polar Software. Thanks to Dirk Domschowski who explained the basics an found the solution. As the s710 scripts deal with a header size of 109 for the S710 watch some header information gets lost. Actually I don't mind, but as soon as I find some time, I'll hhave a look. Regards, Chris To
• Aug 29, 2008

  issue 10 (Wrong sample - right summery data in human readable output) reported by i...@christoph-leiter.de   -   What steps will reproduce the problem? 1. srdcat srd20080829T062534.04803.srd 2. srd2hrm srd20080829T062534.04803.srd 3. What is the expected output? What do you see instead? The error is best seen with the altitide data: On the one hand "Minimum Altitude" and "Maximum Altitude" in the exercise summary are feasible, on the other hand, the sample data show mostly negativ altitudes - and I truly know, that I wasn't diving with my bike this morning :-) What version of the product are you using? On what operating system? Version 0.21 OS: SuSE 11.0 kernel: 2.6.25.5-1.1-default Please provide any additional information below. As srdcat produces wrong data, srd2hrm does so, too. Also the plots produced with srdplot are wrong. The dataviewer "sportstracker", guess you know that, plots right data. So I guess theres a bug in tht srd->hrm conversion. I use a Polar S725x and the old, non Windows XP (uhhhh, the W... word ;-)) compatible IrDA Interface. Last comment: Nevertheless: Great job!!! Chris

  What steps will reproduce the problem? 1. srdcat srd20080829T062534.04803.srd 2. srd2hrm srd20080829T062534.04803.srd 3. What is the expected output? What do you see instead? The error is best seen with the altitide data: On the one hand "Minimum Altitude" and "Maximum Altitude" in the exercise summary are feasible, on the other hand, the sample data show mostly negativ altitudes - and I truly know, that I wasn't diving with my bike this morning :-) What version of the product are you using? On what operating system? Version 0.21 OS: SuSE 11.0 kernel: 2.6.25.5-1.1-default Please provide any additional information below. As srdcat produces wrong data, srd2hrm does so, too. Also the plots produced with srdplot are wrong. The dataviewer "sportstracker", guess you know that, plots right data. So I guess theres a bug in tht srd->hrm conversion. I use a Polar S725x and the old, non Windows XP (uhhhh, the W... word ;-)) compatible IrDA Interface. Last comment: Nevertheless: Great job!!! Chris
• Aug 10, 2008

  issue 9 (Can't find libs710.so.9) commented on by titan232   -   I was getting the same error and the /local.conf fix worked but I have kept trying and I found adding the libstdc++6-4.1-dev libs ( drags in others) allowed a compile without the error,( I already have libstdc++5 and 6 installed) and it is repeatable. I use Debian ( so should work on Ubuntu) and used checkinstall for the first time on the final build "# checkinstall -D make install" which creates a .deb installs it and puts a copy in the .s710 folder. I am using kernel 2.6.26.

  I was getting the same error and the /local.conf fix worked but I have kept trying and I found adding the libstdc++6-4.1-dev libs ( drags in others) allowed a compile without the error,( I already have libstdc++5 and 6 installed) and it is repeatable. I use Debian ( so should work on Ubuntu) and used checkinstall for the first time on the final build "# checkinstall -D make install" which creates a .deb installs it and puts a copy in the .s710 folder. I am using kernel 2.6.26.