[Bug java/42409] org.eclipse.jdt.internal.compiler.batch.GCCMain not found

["jlpoole at pon dot net" <gcc-bugzilla@gcc.gnu.org>]

------- Comment #10 from jlpoole at pon dot net  2010-01-05 02:31 -------
http://gcc.gnu.org/install/finalinstall.html has:
vvvvv
...
We strongly recommend to install into a target directory where there is no
previous version of GCC present.
...
Installation into a temporary staging area or into a chroot jail can be
achieved with the command

     make DESTDIR=path-to-rootdir install

where path-to-rootdir is the absolute path of a directory relative to which all
installation paths will be interpreted. Note that the directory specified by
DESTDIR need not exist yet; it will be created if necessary. 
^^^^^
I think those very words caused me to think what I did was a correct way of
isolating the compiler without affecting my existing one.

"make" has finished (about 21 hours) and I ran:
  make check-target-libjava
which produced:
                === libjava Summary ===

# of expected passes            2561
# of unexpected failures        6
# of untested testcases         6

Question:  In light of the documentation quoted above, if I do not use the
DESTDIR, then to install, should I simply run:

  make install

and my previous use of --prefix=/usr/local/gcj will cause everything to go
under /usr/local/gcj and not affect my existing gcc?  I'm really nervous that
running make install will cause it to supplant my existing GCC.  I also want to
make sure there is not an additional parameter that should be provided to
assure isolation of this installation.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42409