[manül]

By trying to install the addon on a Linux/Arm device, the addon can not be loaded. The XBMC log tells:

/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found

My XBMC build seemes to use an other version.

The message is telling you your libstdc++/gcc is too old. I'm cross-compiling with crosstool-ng 1.18.0 and it's default gcc version 4.7.3.

To solve this little problem I compiled the source from 'https://github.com/manuelm/xbmc-pvr-addons' on my development System, X86 Debian, but 'make zip' only produces the linux-i486-version. What must been changed to make linux-arm-Versions?
Thanks a lot!

Meanwhile compiling was succesful. I called

./configure --host=arm--linux

.
But the problem still remains the same. After installing the addon could not be loaded:

ERROR: Unable to load /root/.xbmc/addons/pvr.dvbviewer/XBMC_dvbviewer.pvr, reason: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /root/.xbmc/addons/pvr.dvbviewer/XBMC_dvbviewer.pvr)

Any suggestions?

You haven't set up a cross-compile toolchain. Use crosstool-ng. It's really easy (compared to the manual steps).
And you'll have to use --host=arm-unknown-linux-gnueabi

---

I have found a Bug. When XBMC is started under a proxy server the addon does not start unfortunately. Is there a solution for this?

I wouldn't call this a real bug. The plugin is using methods provided by XBMC to fetch HTTP sites. XBMC is using libcurl. Hence libcurl tries to communicate with the RS using the specified proxy. There's no UI to specify proxy exceptions but libcurl supports environment variables.

Environment Variables

libcurl automatically checks and uses a set of environment variables to know what proxies to use for certain protocols. The names of the variables are following an ancient de facto standard and are built up as "[protocol]_proxy" (note the lower casing). Which makes the variable 'http_proxy' checked for a name of a proxy to use when the input URL is HTTP. Following the same rule, the variable named 'ftp_proxy' is checked for FTP URLs. Again, the proxies are always HTTP proxies, the different names of the variables simply allows different HTTP proxies to be used.

The proxy environment variable contents should be in the format "[protocol://][user:password@]machine[:port]". Where the protocol:// part is simply ignored if present (so http://proxy and bluerk://proxy will do the same) and the optional port number specifies on which port the proxy operates on the host. If not specified, the internal default port number will be used and that is most likely *not* the one you would like it to be.

There are two special environment variables. 'all_proxy' is what sets proxy for any URL in case the protocol specific variable wasn't set, and 'no_proxy' defines a list of hosts that should not use a proxy even though a variable may say so. If 'no_proxy' is a plain asterisk ("*") it matches all hosts.

from http://curl.haxx.se/libcurl/c/libcurl-tutorial.html