|
I upgraded from synergy 1.4.3 to 1.4.5 and have been receiving the following when trying to start the synergy server: $ synergys -c synergy.conf synergys: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by synergys) $ Can anyone point me in the right direction, I have become dependent upon synergy - it keeps keyboard clutter from occurring. TIA, Thomas |
|
Ok, go here...http://pkgs.org/download/libstdc++.so.6%28GLIBCXX_3.4.14%29...download the file labeled...libstdc++4.6.2-1.fc17.1.i686.rpm or the 64 bit version. Open it up with archive manager...open the first folder and copy the next folder over the usr folder and you should be set. You might have to be root in order to do this. After that, it should work like a charm....Hope that helps. Thanks for the reply, but I said under Ubuntu, and I cannot see any packages for Ubuntu here. Should any one of these be compatible with Ubuntu 10.04? AFAIK, Ubuntu uses .deb files, instead of .rpm, right? Thanks.
(07 Dec '11, 09:12)
GT_Force
This will work for Ubuntu as I too am using Ubuntu, 10.04 Lucid. Do as I had instructed above and it will work. Worked for me just find. You just have to treat the RPM package as an archive and manually install the files yourself. Yes, Ubuntu uses .deb packages, but the .rpm packages are viewed as archives and you can open then just as easy as a zip or tarball.
(09 Dec '11, 08:36)
pcelf
Ah, ok, thanks. I'll try now.
(09 Dec '11, 09:15)
GT_Force
There's no 64-bit version for FC on that page. Would any of the other 64bit packages be fine? e.g., libstdc++46-32bit-4.6.2_20111026-1.1.4.x86_64.rpm ? BTW, this has x86_64 at the end, but it says 32bit in the file name. Is this the 64bit version or 32 bit one? Very confusing! Thanks.
(09 Dec '11, 09:22)
GT_Force
While waiting for a reply, I got lib64stdc++6-4.6.2-6-mdv2012.0.x86_64.rpm and extracted it to my /usr/ folder. synergy still says: synergyc: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by synergyc) and when I checked, libstdc++.so.6 is present under /usr/lib /usr/lib32 and /usr/lib64 so, how come synergy cannot find it?
(09 Dec '11, 09:43)
GT_Force
Try rebooting your computer. If that doesn't work, then try using the 32 bit version of Synergy. I'm using the 32 bit version of Ubuntu because of the problems associated with running 64 bit programs and the lack of 64 bit programs that I like to use. I'm using a dual core AMD processor so I have the ability of running 64 bit, but it seems that I have less problems getting programs to work in 32, but 32 bit programs should run fine under the 64 bit OS.
(09 Dec '11, 22:18)
pcelf
I'm running a MacOSX 10.7 (Lion) server and Ubuntu 10.04 LTS client. Tried Synergy 1.4.7: very unstable. Constantly lost control of the keyboard, including directly connected keyboard. Regained control by suspending client, but lost control again. I then tried 1.3.8 on both systems; got above mentioned error (GLIBCXX_3.4.14 not found) on Ubuntu. I reverted to v1.3.1 (repository version), and things worked fine. Upgraded Mac to 1.3.8, and it's working fine connecting to 1.3.1 on Ubuntu.
(09 Apr '12, 23:51)
donls
I originally tried upgrading the Mac to 1.4.7, but the two versions do not talk to each other at all.
(09 Apr '12, 23:52)
donls
showing 5 of 9
show 4 more comments
|
|
Here's a way to unpack the .rpm file on an Ubuntu machine: Install package rpm2cpio using the Synaptic Package Manager. In the directory containing the .rpm file, do: % rpm2cpio ./libstdc++-4.6.3-2.fc16.i686.rpm | cpio -idmv It should unpack and create a usr directory. Under that will be lib and share directories. In the lib directory you should see: libstdc++.so.6 libstdc++.so.6.0.16. Run: % strings ./libstdc++.so.6 | grep GLIBCXX GLIBCXX_3.4.14 will be in the list. Hope this helps... |
OK, I give up. I try to use the most current version of software that I use, but in the case of synergy, I can't.
I downloaded the 1.4.3 version of synergy (and will keep it just in case), completely uninstalled 1.4.5, then installed the 1.4.3 version on both my server and client workstations. All went well, and 1.4.3 runs just fine on both (whew!).
I'll just have to skip the 1.4.5 version, and possibly all subsequent versions if the same problem arises on them.
If anyone is curious, I am running Ubuntu 10.4 on both workstations - soon to be Ubuntu 11.10, maybe.
I have the same error with 1.3.8 under Ubuntu 10.04. How can I fix it? Thanks.