So, as before, you need to symlink libssl and libcrypto, but this time, you need to do the symlinking in the normal 64bit lib path.
/usr/lib64$ sudo ln -s libssl.so.1.0.1k libssl.so.1.0.0 /usr/lib64$ sudo ln -s libcrypto.so.1.0.1k libcrypto.so.1.0.0
This is despite the eagle installer saying that it needs the 32bit libraries installed!
I’ve spoken about this before, but here’s how to install current Eagle 6.5.0 on Fedora 18 64bit.
As before, this may be incomplete for a fresh install, ie, I’ve already installed all the 32bit compat libs. But Eagle expects to find OpenSSL 1.0.0. No other version at all.
You need openssl-libs.i686 to be installed, but that will be 1.0.1e, and none of the existing symlinks are suitable.
$ sh ./eagle-lin-6.5.0.run /tmp/eagle-setup.11607/eagle-6.5.0/bin/eagle: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
However, you can just symlink it a bit more…
/usr/lib $ sudo ln -s libssl.so.1.0.1e libssl.so.1.0.0 /usr/lib $ sudo ln -s libcrypto.so.1.0.1e libcrypto.so.1.0.0
Bash completion is normally pretty awesome. You can even tab complete hostnames to ssh, if you’ve ssh’d to them before. It can complete arguments to all sorts of commands, and there’s even a python module that will let you provide completion for your custom command.
And this is all handled by plugins, so if you are executing something new/different, you get plain old regular completion of files and directories. This mostly all works, but I ran into a problem with a python script I’d written the other day, and I have no solution at all, only a workaround.
In all cases I expect to get full path plus file completion and prompting as my command is “unknown”
| Command | Outcome |
|---|---|
asdfasdf fileprefix[tab]
| Works perfectly |
python my-script.py fileprefix[tab]
| Works perfectly |
python my-script.py --my-argument fileprefix[tab]
| only completes directories! |
chmod +x myscript.py
| Works perfectly |
I can only assume there’s a bug in the python completion module? No idea how to diagnose it further though. Having to make my own scripts executable isn’t the end of the world though, so it works for now. This was with bash 4.25.45(1) on Fedora 18, and bash-completion version 2.1, fwiw
Eagle is only provided as a 32bit package for linux, even as of version 6.3. I’m still using 5.x, for compatibility reasons, so I was trying to get it installed on my newish Fedora 17 64 bit install. Eagle’s #1 FAQ item is how to do this, but it’s for fedora 10, and some of the packages have changed. You also don’t need to install as many, as some of them will be pulled in as dependencies.
There, much better.
Updated with corrections 2013-Nov-18