I used the Software Manager in Linux Mint to install Eclipse Platform. It was working yesterday, however, now whenever I run it I get the following error message:
The Eclipse executable launcher was unable to locate its companion shared library.
I tried uninstalling it and then installing it again. Much to my confusion, this did not work. The error message still persists. It implies Eclipse requires a shared dependency that it cannot find. Is there anyway to find out what this is and install it? I've tried 'apt-get dist-upgrade' to update packages but this didn't resolve the issue at hand.
I have been using linux and Eclipse for years, but I would never suggest anyone install Eclipse from the platform repositories for any distribution.
Get your eclipse zips directly from Eclipse.org
Personally, I would just "Google it." (Or, in my case, "DuckDuckGo it.") Put the exact error-message text in double quotes to tell the search-engine that you are looking for the exact phrase.
DDG promptly referred me to this page: http://veeddie.blogspot.com/2010/06/eclipse-executable-launcher-was-unable.html
Related
I'm trying to install Kieran Healy's Emacs Starter Kit (https://github.com/kjhealy/emacs-starter-kit) on linux arch (I have also tried on a Mint installation, running into the same errors), but I'm having quite some trouble.
After deleting my ~/.emacs.d and installing the starter kit, emacs starts installing packages, but runs into a 'Package magit- is not available'-error. Other Melpa-packages are installing fine. An m-x refresh-contents doesn't make a difference, and neither does an m-x install-package magit.
I am able to install magit if I temporarily rename my .d.emacs and run with a fresh .emacs, and if I, after installation of magit, enable the starter kit again, emacs will load the installed magit-package perfectly fine. It does stall again, on several other packages (ipython, typopunct), in exactly the same manner.
If I comment out the 'require of these three packages, installation seems to work, but stalls on a not found 'ob-shell (as in this question: https://emacs.stackexchange.com/questions/21366/should-i-have-removed-shell-t-to-clear-an-ob-shell-initialization-error). This is in addition to several other errors that seem to indicate a not-complete installation as I try to continue use of emacs.
I have not been able to find any documentation relating to this. Appearently, missing packages are not uncommon with old emacs-installations, but as I am using a 25.1.1 install, this does not seem to be the problem.
Any ideas going forward?
The issue with magit was indeed solved a little while ago. The issue with ipython that apc raised exists because that's a package from the Marmalade repo, which needs to be added manually to the list of repositories. To install it, just execute the following code in the console.
M-x package-refresh-contents [RET]
M-: (add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/"))
M-x package-refresh-contents [RET]
M-x package-install [RET] ipython
I am comparatively new to Linux. I am running Fedora 64 bit at my PC. I am having difficulty setting up ddd with bashdb. I am able to install it using yum but when I run it for bashdb, the software environment for ddd comes up but it keeps on working for infinite time, unless I manually kill it.
I used google to know what the problem is and came to know many people are having same problem, when using linux's package installers. It has bugs so I have to compile the latest source and install it manually. So I downloaded the source and tried to ./configure, it produced the following error and exited:
configure: error: Cannot find termcap compatible library
I searched again and found out I need termcap library at my PC, here:
https://lists.gnu.org/archive/html/bug-ddd/2013-01/msg00004.html
http://www.cplusplus.com/forum/unices/58299/
I used yum to install ncurses but found out it is already installed. Used locate to find the path of ncurses and passed it to configure using following commands:
sudo ./configure --with-termlib-libraries=/lib/libncurses.so.5
sudo ./configure --with-termlib-libraries=/lib/libncurses.so.5.9
Still, I am having the same error.
It is very frustrating because I have tried almost everything I found on internet. May be, there is a minor point that I am overlooking due to my inexperience. My main concern is to be able to debug complex bash scripts that I am going to develop in near future. I am not very comfortable with command line debugging i.e. without an interface. Any tips/advice that, can get me going with debugging with some other application may be, are also welcomed
I installed the ncurses development package to get past this problem:
sudo yum install ncurses-devel*
This might be more of a CYGWIN question than a Nodejs but here goes.
I installed Cygwin yesterday and on the packages selection I just clicked next as it looked like most were pre-selected, and then today read this guide http://boxysystems.com/index.php/step-by-step-instructions-to-install-nodejs-on-windows/ on installing nodejs.
The ./configure had an error that it was unable to remap python lib-dynload/itertools.dll to same address as parent. As the process still completed I tried the make command, but it fails on the same error.
So, I opened cygwin setup.exe and this time I clicked the source checkbox for all the Python packages. But still get the same error. Should I now go to Cygwin and check all the source packages for the Make packages, delete it and reinstall from scratch using the above guide. Or something else?
Any help gratefull received/
Use the official 0.5.x windows build from http://nodejs.org/#download - you just have to download a .exe file and you can start it.
Versions 0.5.X have problems with Cygwin and because of developing clean Windows version Cygwin environment is now unsupported. Stable version 0.4.12 builds on Cygwin with no problems. If you want to use node.js unstable 0.5.X branch on Windows use windows build at official node.js site.
check this out:
https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-(Windows)
Update Sept 1, 2011 -- as of today, v0.5.5 does not build on Cygwin (errors on make). Use v.0.5.4 (ie. follow instructions below and use "git checkout v0.5.4".
https://github.com/joyent/node/wiki/API-changes-between-v0.4-and-v0.6
Cygwin build is no longer supported. Use native windows builds instead.
When I try to install/update any plugin from Help -> Install New Software I receive error messages like this:
No repository found at http://download.eclipse.org/releases/galileo.
or
Unable to connect to repository http://pydev.org/updates/site.xml
Invalid argument
This happens with all Eclipse versions.
I use Eclipse on Debian Sid.
I had the same problem, try running eclipse with these options:
-vmargs -Djava.net.preferIPv4Stack=true
It worked for me
(see https://lists.launchpad.net/openjdk/msg03123.html)
Try disabling proxies inside Eclipse. This helped me once.
Here are some generic eclipse error resolution steps I use:
1) Try run eclipse with the -clean option. This should cleanup some stuff. No clue if it helps with your problem, but maybe worth a try?
2) Delete .metadata directory (or move it temporarily away) from your workspace and run eclipse with the -clean option again.
3) (Skip if you have tried this) Try download another eclipse installation into another local directory and try to see if that works out of the box. If it works, your former eclipse installation was bugged. If it does not work, I suggest checking your general network access to the specific urls you mention.
I needed to install ibus on Ubuntu 19.04 LTS and shortly after doing so I started getting this error when trying any file in Eclipse 2019.
org.eclipse.swt.SWTError: No more handles
I tried installing the newest version thinking something broke in Eclipse, but I couldn't even install because I got the same error in the installer.
I didn't realize right away that ibus was the cause because I didn't try using Eclipse for several hours after installing it.
After a lot of searching and trying just about everything, the answer turned out to be the need to set the GTK mode before launching Eclipse.
export GTK_IM_MODULE="ibus"
To make my life easier in the future, I created a script file to do this any time I started Eclipse. This is a simple text file with the executable flag set.
#/bin/bash
export GTK_IM_MODULE="ibus"
~/Programs/eclipse/php-2019-03/eclipse/eclipse
I hope this saves others a great deal of searching.