On 2016-02-05 22:38, Martin Helm wrote:

Am 05.02.2016 um 22:22 schrieb Carlos E. R.:

...

I have libstdc++6-4.8.1_20130909-3.2.1.x86_64

Does it really want version 3.4.21, and the version 3.2.1 doesn't work? What can I do? This is openSUSE 13.1.

Your libstdc++ is too old not too new.

Yes, of course.

You misinterpret what the version requirement means it does not as you suspect represent the version of the gcc your libstdc++ belongs too. But the "features" your library provides. You can check with rpm -q --provides libstdc++6-4.8.1_20130909-3.2.1.x86_64 the GLIBCXX versions which this package provides

Ah. I see where the numbers come from, now. Telcontar:~ # rpm -q --provides libstdc++6-4.8.1_20130909-3.2.1.x86_64 libstdc++.so.6()(64bit) libstdc++.so.6(CXXABI_1.3)(64bit) libstdc++.so.6(CXXABI_1.3.1)(64bit) libstdc++.so.6(CXXABI_1.3.2)(64bit) libstdc++.so.6(CXXABI_1.3.3)(64bit) libstdc++.so.6(CXXABI_1.3.4)(64bit) libstdc++.so.6(CXXABI_1.3.5)(64bit) libstdc++.so.6(CXXABI_1.3.6)(64bit) libstdc++.so.6(CXXABI_1.3.7)(64bit) libstdc++.so.6(CXXABI_TM_1)(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) libstdc++.so.6(GLIBCXX_3.4.1)(64bit) libstdc++.so.6(GLIBCXX_3.4.10)(64bit) libstdc++.so.6(GLIBCXX_3.4.11)(64bit) libstdc++.so.6(GLIBCXX_3.4.12)(64bit) libstdc++.so.6(GLIBCXX_3.4.13)(64bit) libstdc++.so.6(GLIBCXX_3.4.14)(64bit) libstdc++.so.6(GLIBCXX_3.4.15)(64bit) libstdc++.so.6(GLIBCXX_3.4.16)(64bit) libstdc++.so.6(GLIBCXX_3.4.17)(64bit) libstdc++.so.6(GLIBCXX_3.4.18)(64bit) libstdc++.so.6(GLIBCXX_3.4.19)(64bit) libstdc++.so.6(GLIBCXX_3.4.2)(64bit) libstdc++.so.6(GLIBCXX_3.4.3)(64bit) libstdc++.so.6(GLIBCXX_3.4.4)(64bit) libstdc++.so.6(GLIBCXX_3.4.5)(64bit) libstdc++.so.6(GLIBCXX_3.4.6)(64bit) libstdc++.so.6(GLIBCXX_3.4.7)(64bit) libstdc++.so.6(GLIBCXX_3.4.8)(64bit) libstdc++.so.6(GLIBCXX_3.4.9)(64bit) libstdc++6 = 4.8.1_20130909-3.2.1 libstdc++6(x86-64) = 4.8.1_20130909-3.2.1 Telcontar:~ # `GLIBCXX_3.4.21' is not there, it stops at 3.4.19. Any solution with the tor bundle? I see a packaged "tor" in the repo, but it is the router, not the bundle. Search for "tor" obtains hundreds of hits, but nothing obvious. Maybe report the problem to the tor people, if they could be interested :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-02-05 23:46, Martin Helm wrote:

...

Maybe report the problem to the tor people, if they could be interested :-?

in which directory did you install? I see that the bundle contains a libstdc++6 and the startup script sets the library path

LD_LIBRARY_PATH="${HOME}/TorBrowser/Tor/" export LD_LIBRARY_PATH

to the directory which contains it, but is only correct if it is installed in ~/TorBrowser

On "~/tor-browser_en-US". I'll try "~/TorBrowser". cer@Telcontar:~/TorBrowser> ./start-tor-browser --verbose ./start-tor-browser: line 266: [: 64: unary operator expected ./start-tor-browser: line 367: ./firefox: No such file or directory cer@Telcontar:~/TorBrowser> cer@Telcontar:~/tor-browser_en-US> ./start-tor-browser --verbose ./start-tor-browser: line 266: [: 64: unary operator expected ./start-tor-browser: line 367: ./firefox: No such file or directory cer@Telcontar:~/tor-browser_en-US> There is no "${HOME}/TorBrowser/Tor/" directory. That "Tor" subdirectory does not exist. This was downloaded by tor itself as an update. I think I must get the entire bundle again. I downloaded "tor-browser-linux64-5.5.1_en-US.tar.xz". It contains: /tor-browser_en-US/Browser No "Tor" subdirectory there. I follow the instructions here: https://www.torproject.org/projects/torbrowser.html.en#linux Ah, it says the right startup script is ./start-tor-browser.desktop, not ./start-tor-browser It starts. That was my error, wrong script. It has changed from the version I used before. Thanks! -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)