Difficulties installing eclim in linuxmint 17.

[Ben Smith]

After I ran into difficulties running the graphical installer at someone’s suggestion I tried to build from source instead. But I still got an error.
Here are the commands I used and everything that was subsequently output in the terminal.

sudo ant "-Declipse.home=/opt/eclipse"
[sudo] password for username:
Buildfile: /home/username/eclim/build.xml

deploy:

gant:
     [echo] ${eclipse}: /opt/eclipse
     [echo] # Skipping org.eclim.pydev, missing org.python.pydev.feature
     [echo] # Skipping org.eclim.dltkruby, missing org.eclipse.dltk.ruby
     [echo] # Skipping org.eclim.sdt, missing org.scala-ide.sdt.feature
     [echo] # Skipping org.eclim.wst, missing org.eclipse.wst.web_ui.feature
     [echo] # Skipping org.eclim.cdt, missing org.eclipse.cdt
     [echo] # Skipping org.eclim.adt, missing com.android.ide.eclipse.adt.feature
     [echo] # Skipping org.eclim.groovy, missing org.codehaus.groovy.jdt.patch
     [echo] # Skipping org.eclim.dltk, missing org.eclipse.dltk.core
     [echo] # Skipping org.eclim.pdt, missing org.eclipse.php
     [echo] Plugins:
     [echo]   org.eclim.jdt
deploy:
deploy.eclipse:
build:
build.eclipse:
init:
     [echo] eclim.version: 2.4.0.4-gb30be77
     [echo] eclim.release: 2.4.0
     [echo] eclim.release.indigo: none
------ init
     [echo]
     [echo] building plugin: org.eclim
    [mkdir] Created dir: /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.4-gb30be77
      [jar] Building jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.4-gb30be77/eclim.jar
     [copy] Copying 42 files to /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.4-gb30be77
org.eclim.build.eclipse:
     [exec] checking for gcc... gcc
     [exec] configure: error: C compiler cannot create executableschecking for C compiler default output file name...
     [exec] See `config.log' for more details.
     [exec]
     [exec] Result: 77
     [exec] make: *** No targets specified and no makefile found.  Stop.
     [exec] Result: 2

BUILD FAILED
/home/username/eclim/build.xml:32: The following error occurred while executing this line:
/home/username/eclim/build.xml:156: : Warning: Could not find file /home/username/eclim/org.eclim/nailgun/ng to copy.

I am not seeing anything called nailgun in the eclim folder that was created when I cloned the repo.

[Ben Smith]

[EDIT] I don't see a way to edit my OP so I just wanted to say to ignore the last sentence I do have nailgun I just was not looking in the right place.

[Eric Van Dewoestine]

On 2014-08-25 17:24:35, Ben Smith wrote:
> After I ran into difficulties running the graphical installer at someone’s
> suggestion I tried to build from source instead. But I still got an error.
> Here are the commands I used and everything that was subsequently output in
> the terminal.
>

> [exec] checking for gcc... gcc
> [exec] configure: error: C compiler cannot create executableschecking
> for C compiler default output file name...
> [exec] See `config.log' for more details.
> [exec]
> [exec] Result: 77
> [exec] make: *** No targets specified and no makefile found. Stop.
> [exec] Result: 2

You are receiving the same error that would occur from the gui
installer, which is that you're unable to build the nailgun ng
executable.

Was a config.log file created, possibly in your
~/eclim/org.eclim/nailgun/ dir? If so, please post the contents from
that, otherwise there any number of possibilities as to why your c
toolchain would fail to configure nailgun (issue with ld, gcc, etc).

Re-installing your system's 'build-essential' package _may_ solve the
problem, but I can't say for sure.

--
eric

[Ben Smith]

What is the build essential package and how do i reinstall it? There is indeed a config.log file in the ~/eclim/org.eclim/nailgun dir here are its contents:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by ng configure 0.7.1, which was
generated by GNU Autoconf 2.61.  Invocation command line was

  $ /home/username/eclim/org.eclim/nailgun/configure

## --------- ##
## Platform. ##
## --------- ##

hostname = username-K53TA
uname -m = x86_64
uname -r = 3.13.0-24-generic
uname -s = Linux
uname -v = #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1734: checking for gcc
configure:1750: found /usr/bin/gcc
configure:1761: result: gcc
configure:1999: checking for C compiler version
configure:2006: gcc --version >&5
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2009: $? = 0
configure:2016: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
configure:2019: $? = 0
configure:2026: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:2029: $? = 4
configure:2052: checking for C compiler default output file name
configure:2079: gcc    conftest.c  >&5
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: cannot find -lc
/usr/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:2082: $? = 1
configure:2120: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "ng"
| #define PACKAGE_TARNAME "ng"
| #define PACKAGE_VERSION "0.7.1"
| #define PACKAGE_STRING "ng 0.7.1"
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2127: error: C compiler cannot create executables

See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_prog_ac_ct_CC=gcc

## ----------------- ##
## Output variables. ##
## ----------------- ##

CC='gcc'
CFLAGS=''
CPP=''
CPPFLAGS=''
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
GREP=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
OBJEXT=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME='ng'
PACKAGE_STRING='ng 0.7.1'
PACKAGE_TARNAME='ng'
PACKAGE_VERSION='0.7.1'
PATH_SEPARATOR=':'
SHELL='/bin/bash'
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build_alias=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME "ng"
#define PACKAGE_TARNAME "ng"
#define PACKAGE_VERSION "0.7.1"
#define PACKAGE_STRING "ng 0.7.1"
#define PACKAGE_BUGREPORT ""

configure: exit 77

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Eric Van Dewoestine]

On 2014-08-26 09:23:16, Ben Smith wrote:
> What is the build essential package and how do i reinstall it?

$ sudo apt-get install build-essential

> There is
> indeed a config.log file in the ~/eclim/org.eclim/nailgun dir here are its
> contents:
>

> ...

> configure:2079: gcc conftest.c >&5
> /usr/bin/ld: cannot find crt1.o: No such file or directory
> /usr/bin/ld: cannot find crti.o: No such file or directory
> /usr/bin/ld: cannot find -lc
> /usr/bin/ld: cannot find crtn.o: No such file or directory
> collect2: error: ld returned 1 exit status

> ...

This is the error which is causing the build failure. I'm not very
familiar with the debian/ubuntu toolchain, so if re-installing
build-essential doesn't do the trick you may need to consult an ubuntu
forum. This error isn't unique to eclim/nailgun. You'd presumably get
this same error attempting to configure other source installs as well.

> --
> You received this message because you are subscribed to the Google Groups "eclim-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to eclim-user+...@googlegroups.com.
> To post to this group, send email to eclim...@googlegroups.com.
> Visit this group at http://groups.google.com/group/eclim-user.
> For more options, visit https://groups.google.com/d/optout.

--
eric

[Ben Smith]

Re-installing build-essential worked! Thank you so much. May I ask what build-essential is and why you suspected I needed to reinstall it. I am also curious what might have caused my build-essential to be messed up as this linux installation is relatively new.

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Ben Smith]

Also for some reason when I try to ping eclim with vim it gives me an error telling me that PingEclim is not an editor command.

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Eric Van Dewoestine]

On 2014-08-26 17:09:56, Ben Smith wrote:
> Re-installing build-essential worked! Thank you so much. May I ask what
> build-essential is

build-essential is the debian/ubuntu package which pulls in the build
toolchain (make, gcc, libc-dev, etc) which are necessary to build
native apps.

> and why you suspected I needed to reinstall it.

Since running configure for nailgun (a native c app) failed, chances
were that one of the build-essential packages were involved. There
were a lot of other possibilities, but that one seems the most likely.

> I am also curious what might have caused my build-essential to be
> messed up as this linux installation is relatively new.

That I wouldn't know. It could be that you had some of the
build-essential packages already installed (perhaps as dependencies
for some other packages), but not all of them, so installing
build-essential explicitly pulled in what was missing.

[Eric Van Dewoestine]

On 2014-08-26 18:23:07, Ben Smith wrote:

> Also for some reason when I try to ping eclim with vim it gives me an error
> telling me that PingEclim is not an editor command.

If you installed using sudo (not recommended), then the vim files were
probably deployed to /root/.vim, which your regular user can't access,
and so none of the eclim commands are defined.

[Ben Smith]

The reason I did a sudo ant -Declipse.home=/opt/eclipse was because just doing ant -Declipse.home=/opt/eclipse gave me the following error:

 ant -Declipse.home=/opt/eclipse     

Buildfile: /home/username/eclim/build.xml

deploy:

gant:
     [echo] ${eclipse}: /opt/eclipse
     [echo] # Skipping org.eclim.pydev, missing org.python.pydev.feature
     [echo] # Skipping org.eclim.dltkruby, missing org.eclipse.dltk.ruby
     [echo] # Skipping org.eclim.sdt, missing org.scala-ide.sdt.feature
     [echo] # Skipping org.eclim.wst, missing org.eclipse.wst.web_ui.feature
     [echo] # Skipping org.eclim.cdt, missing org.eclipse.cdt
     [echo] # Skipping org.eclim.adt, missing com.android.ide.eclipse.adt.feature
     [echo] # Skipping org.eclim.groovy, missing org.codehaus.groovy.jdt.patch
     [echo] # Skipping org.eclim.dltk, missing org.eclipse.dltk.core
     [echo] # Skipping org.eclim.pdt, missing org.eclipse.php
     [echo] Plugins:
     [echo]   org.eclim.jdt
deploy:
deploy.eclipse:
build:
build.eclipse:
init:

     [echo] eclim.version: 2.4.0.5-gff55d36

     [echo] eclim.release: 2.4.0
     [echo] eclim.release.indigo: none
------ init
     [echo]
     [echo] building plugin: org.eclim

BUILD FAILED
/home/username/eclim/build.xml:32: The following error occurred while executing this line:

/home/username/eclim/build.xml:156: : /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36/eclim.jar is read-only.

This happened again when I ran the uninstaller and tried to re-install without sudo to deal with the "not an editor command" issue.

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Eric Van Dewoestine]

That file is read only because you previously built as root, so all
the eclim/build/* files are now owned by root, which your regular user
is not permitted to modify. You can fix this part of the problem
using:

$ sudo ant clean

However, you'll have to manually delete the org.eclim* dirs/files from
your /opt/eclipse/plugins directory, and also manually delete the vim
files from /root/.vim (.vim/plugin/eclim.vim and .vim/eclim/)

After you've done that, I'd recommend then installing eclim using the
gui installer (not as root).

> This happened again when I ran the uninstaller and tried to re-install
> without sudo to deal with the "not an editor command" issue.

Not sure what that means. You got some other error running the
installer?

[Ben Smith]

Thank you very much for all your help thus far. I am sorry this is taking so long. I am really starting to wonder though if I will ever be able to get this thing working. So here is what I did

1. Went into the eclim folder created by the git clone and ran sudo ant clean as instructed
2. Went into /opt/eclipse tried doing ls and ls -a nothing with eclim in the name.
3. Went into home/username/.vim/plugin tried doing ls and ls -a nothing with eclim in the name.
4. Went into home/username/.vim/after there were a few things with eclim and different programming languages in the names, I deleted all these files.
5. Used su and became super user then went into root/.vim/plugins ls and ls -a again show nothing with eclim in the name
6. Using ls -a in /root I saw a file called .eclim so I deleted it.
7. Tried to run the graphical installer got some kind of error.
8. Tried to build from source got some kind of error the last line said something about not being able to delete some kind of file in a directory in  /opt/eclipse/features/
9. I looked in /opt/eclipse/features/ and saw a directory called eclim.2.4.0.5 or something like that, I figured this was something I was supposed to get rid of earlier so used su to become superuser and I deleted the whole directory.

So where I am now neither the graphical nor build from source work still. I have pasted the graphical installer error followed by the build from source error in blue (I tried to just attach text files but it said something about them not being allowed).

java.lang.RuntimeException: error: An error occurred while collecting items to be installed
 session context was:(profile=epp.package.standard, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
 No repository found containing: osgi.bundle,org.eclim,2.4.0.5-gff55d36
 No repository found containing: osgi.bundle,org.eclim.core,2.4.0.5-gff55d36
 No repository found containing: osgi.bundle,org.eclim.jdt,2.4.0.5-gff55d36
 No repository found containing: osgi.bundle,org.eclim.vimplugin,2.4.0.5-gff55d36
Application failed, log file location: /home/sifat/.eclipse/org.eclipse.platform_4.4.0_1473617060_linux_gtk_x86_64/configuration/1409180914235.log
 out: Installing org.eclim.installer.feature.group 2.4.0.
Installation failed.

    at org.eclim.installer.step.EclipseInfo.installInstallerPlugin(EclipseInfo.java:183)
    at org.eclim.installer.step.EclipseInfoStep$1.run(EclipseInfoStep.java:67)
    at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
    at java.security.AccessController.doPrivileged(Native Method)
    at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
    at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
    at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
    at java.lang.Thread.run(Thread.java:744)

    [mkdir] Created dir: /home/usernam/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36
      [jar] Building jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36/eclim.jar
     [copy] Copying 45 files to /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36
org.eclim.build.eclipse:
     [copy] Copying 1 file to /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36/bin
      [jar] Updating jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim_2.4.0.5-gff55d36/lib/nailgun-0.7.1.jar
------ org.eclim.build.eclipse
     [echo]
     [echo] building plugin: org.eclim.core
    [mkdir] Created dir: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36
      [jar] Building jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36/eclim.core.jar
     [copy] Copying 7 files to /home/username/eclim/build/temp/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36
     [echo]
     [echo] building plugin: org.eclim.vimplugin
    [mkdir] Created dir: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.vimplugin_2.4.0.5-gff55d36
      [jar] Building MANIFEST-only jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.vimplugin_2.4.0.5-gff55d36/eclim.vimplugin.jar
     [copy] Copying 6 files to /home/username/eclim/build/temp/eclipse/plugins/org.eclim.vimplugin_2.4.0.5-gff55d36
org.eclim.vimplugin.build.eclipse:
      [jar] Updating jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.vimplugin_2.4.0.5-gff55d36/eclim.vimplugin.jar
------ org.eclim.vimplugin.build.eclipse
     [echo]
     [echo] building plugin: org.eclim.jdt
    [mkdir] Created dir: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.jdt_2.4.0.5-gff55d36
      [jar] Building jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.jdt_2.4.0.5-gff55d36/eclim.jdt.jar
     [copy] Copying 14 files to /home/username/eclim/build/temp/eclipse/plugins/org.eclim.jdt_2.4.0.5-gff55d36
org.eclim.jdt.build.eclipse:
      [jar] Building jar: /home/username/eclim/build/temp/eclipse/plugins/org.eclim.jdt_2.4.0.5-gff55d36/eclim-testng.jar
------ org.eclim.jdt.build.eclipse
------ build.eclipse
build.vim:
   [delete] Deleting directory /home/username/eclim/build/temp/vim
    [mkdir] Created dir: /home/username/eclim/build/temp/vim
     [copy] Copying 48 files to /home/username/eclim/build/temp/vim/org.eclim.core
     [copy] Copying 2 files to /home/username/eclim/build/temp/vim/org.eclim.vimplugin
     [copy] Copying 68 files to /home/username/eclim/build/temp/vim/org.eclim.jdt
------ build.vim
------ build
     [copy] Copying 78 files to /opt/eclipse/plugins

BUILD FAILED
/home/username/eclim/build.xml:32: The following error occurred while executing this line:

/home/username/eclim/build.xml:156: : Failed to copy /home/username/eclim/build/temp/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36/META-INF/MANIFEST.MF to /opt/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36/META-INF/MANIFEST.MF due to failed to create the parent directory for /opt/eclipse/plugins/org.eclim.core_2.4.0.5-gff55d36/META-INF/MANIFEST.MF

Total time: 5 seconds
zsh: exit 1     ant -Declipse.home=/opt/eclipse

[Eric Van Dewoestine]

On 2014-08-27 16:26:19, Ben Smith wrote:
> Thank you very much for all your help thus far. I am sorry this is taking
> so long. I am really starting to wonder though if I will ever be able to
> get this thing working. So here is what I did
>
> 1. Went into the eclim folder created by the git clone and ran sudo ant
> clean as instructed
> 2. Went into /opt/eclipse tried doing ls and ls -a nothing with eclim in
> the name.

You should have seen something in /opt/eclipse/plugins and maybe
/opt/eclipse/features. Really at this point, you'd be best off
re-installing eclipse by uninstalling it, making sure all of its
files have been removed (including ~/.eclipse), and then installing it
again. Who know what state its in right now and eclipse can be
finicky.

> 3. Went into home/username/.vim/plugin tried doing ls and ls -a nothing
> with eclim in the name.

Not surprising since we haven't gotten you past the root owned issues
yet.

> 4. Went into home/username/.vim/after there were a few things with eclim
> and different programming languages in the names, I deleted all these files.

I'd be interested to know what was there since eclim doesn't install
anything to .vim/after.

> 5. Used su and became super user then went into root/.vim/plugins ls and ls
> -a again show nothing with eclim in the name

Did you also check /root/.vim/ for an 'eclim' dir? Actually, since you
ran as root, the files could have been installed at
/usr/share/vim/vimfiles, or similar. Try running vim as root and then
run:

:echo &rtp

And check every path in that comma separated list.

> 6. Using ls -a in /root I saw a file called .eclim so I deleted it.
> 7. Tried to run the graphical installer got some kind of error.

I'd have to see the contents of the file[1] referenced in the error to
know what's up, but with all that's going on, re-installing eclipse
would probably be your best bet (as described above).

[1] /home/sifat/.eclipse/org.eclipse.platform_4.4.0_1473617060_linux_gtk_x86_64/configuration/1409180914235.log

> 8. Tried to build from source got some kind of error the last line said
> something about not being able to delete some kind of file in a directory
> in /opt/eclipse/features/

Yeah you obviously can't write to root owned dirs, so you'll have to run
the build like so, but I still recommend reinstalling eclipse and just
sticking to the installer (vacillating back and forth between building
and the installer is only going to make matters more difficult to
troubleshoot):

$ ant \
-Declipse.home=/opt/eclipse \
-Declipse.local=$HOME/.eclipse/org.eclipse.platform_4.4.0_1473617060_linux_gtk_x86_64

> 9. I looked in /opt/eclipse/features/ and saw a directory called
> eclim.2.4.0.5 or something like that, I figured this was something I was
> supposed to get rid of earlier so used su to become superuser and I deleted
> the whole directory.

> So where I am now neither the graphical nor build from source work still. I
> have pasted the graphical installer error followed by the build from source
> error in blue (I tried to just attach text files but it said something
> about them not being allowed).

fyi, I'm going to be updating the eclim build script and installer to
abort when run as root since doing so obviously causes so many issues.
I'm sorry you had to go through this, but in general you should be
weary of building/installing anything as root outside of your package
manager (this is why tools like checkinstall[2] exist for building
root level apps).

[2] https://help.ubuntu.com/community/CheckInstall

> > an email to eclim-user+...@googlegroups.com <javascript:>.

> > > To post to this group, send email to eclim...@googlegroups.com

> > <javascript:>.

[Ben Smith]

So I am trying to do the things you suggested:

1. When I did :echo &rtp I found nothing with eclim in the name in any of the file paths I was able to look in. One strange thing happened though /usr
/share/vim/vimfiles/after , /var/lib/vim/addons/after , /root/.vim/after when I tried to cd these both normally and as root I got messages saying that the directories did not exist. I tried going down one directory at a time and it seemed like it was the last one in each case that did not show up when I did ls or ls -a .

2. I am trying to re-install eclipse but am unsure as to how to completely remove it. I installed it to /opt so I deleted that directory , then i deleted ~/.eclipse like you said. But when I do locate eclipse all sorts of stuff comes up. So I tried doing locate eclipse | xargs rm -rf as root and that seemed to get rid of a bunch of stuff. But when I do locate eclipse lots of stuff still comes up including /opt/eclipse which is really strange cause I definitely deleted that and can't see it anymore. I am very confused in case it was not already obvious its not just eclim I am very new to linux in gen so I have very little idea what I am doing.

 

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Eric Van Dewoestine]

On 2014-08-27 19:08:53, Ben Smith wrote:
> So I am trying to do the things you suggested:
>
> 1. When I did :echo &rtp I found nothing with eclim in the name in any of
> the file paths I was able to look in. One strange thing happened though /usr
> /share/vim/vimfiles/after , /var/lib/vim/addons/after , /root/.vim/after
> when I tried to cd these both normally and as root I got messages saying
> that the directories did not exist. I tried going down one directory at a
> time and it seemed like it was the last one in each case that did not show
> up when I did ls or ls -a .

Those 'after' dirs don't have to exist, so that's normal.

> 2. I am trying to re-install eclipse but am unsure as to how to completely
> remove it. I installed it to /opt so I deleted that directory , then i
> deleted ~/.eclipse like you said. But when I do locate eclipse all sorts of
> stuff comes up. So I tried doing locate eclipse | xargs rm -rf as root and
> that seemed to get rid of a bunch of stuff. But when I do locate eclipse
> lots of stuff still comes up including /opt/eclipse which is really strange
> cause I definitely deleted that and can't see it anymore. I am very
> confused in case it was not already obvious its not just eclim I am very
> new to linux in gen so I have very little idea what I am doing.

The 'locate' command searches from an index which is usually updated
by a cron job, so that's why you are still finding those files after
removing them. Usually there is an 'updatedb' command which refreshes
the locate index, should you want to run that manually.

[Ben Smith]

So does that mean that what I have done is sufficient to have uninstalled eclipse and all I have to do now is reinstall eclipse and then install eclim using the graphical installer?

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Ben Smith]

It worked! I removed all the eclipse files I could find double checked the vim stuff, re-installed eclipse and then ran the graphical installer. I was so relieved when it said installation completely successful and again when I was able to ping eclim successfully! Thank you so much again for all the extensive help you gave me, I could not have done it without you. The only strange thing now is that eclimd seems to be in a different location than the eclipse home directory which if I understand correctly is where your website says it should be. The location is rather long /home/username/.eclipse/org.eclipse.platform_4.4.0_1473617060_linux_gtk_x86_64/eclimd , is there a way I can make it so I don't have to type this in every time I want to start it?

PS. You had mentioned you would be interested to know what those files I deleted in .vim/after I just wanted you to know that the only reason I did not provide them was that I do not remember what they were, sorry. Oh and thanks for teaching me that I should not install things as root I had no idea it could cause so many problems.

On Monday, August 25, 2014 8:24:35 PM UTC-4, Ben Smith wrote:

[Eric Van Dewoestine]

On 2014-08-27 22:30:51, Ben Smith wrote:
> It worked! I removed all the eclipse files I could find double checked the
> vim stuff, re-installed eclipse and then ran the graphical installer. I was
> so relieved when it said installation completely successful and again when
> I was able to ping eclim successfully!

Awesome!

> Thank you so much again for all the
> extensive help you gave me, I could not have done it without you.

Thank you for sticking with it. I'm sorry you had to jump through so
many hoops to get it working.

> The only
> strange thing now is that eclimd seems to be in a different location than
> the eclipse home directory which if I understand correctly is where your
> website says it should be. The location is rather long
> /home/username/.eclipse/org.eclipse.platform_4.4.0_1473617060_linux_gtk_x86_64/eclimd
> , is there a way I can make it so I don't have to type this in every time I
> want to start it?

You can create a symlink to the location of your choice, something
like so:

$ ln -s ~/.eclipse/<long_path>/eclimd ~/eclimd

Then you can run eclimd from the symlink:

$ ~/eclimd

> PS. You had mentioned you would be interested to know what those files I
> deleted in .vim/after I just wanted you to know that the only reason I did
> not provide them was that I do not remember what they were, sorry.

No problem.

> Oh and
> thanks for teaching me that I should not install things as root I had no
> idea it could cause so many problems.

It kind of depends on the program, as to what issues you may or many
not encounter. In most cases the worst that will happen is that files
will be installed to various locations and you won't necessarily know
where they all went. That's why letting your package manager (apt in
your case) install apps is typically the best route.