GCCMain not found & test suite errors fatal?

[John Poole]

On 1/4/2010 3:28 AM, Bryce McKinlay wrote:
> On Sun, Jan 3, 2010 at 6:59 PM, Andrew Haley <aph@redhat.com 
> <mailto:aph@redhat.com>> wrote:
>
>
>     > It was created by configure, which was
>     > generated by GNU Autoconf 2.64.  Invocation command line was
>     >
>     >    $ ../trunk/configure --enable-languages=java
>
>     Oh right, that's the problem then.  You need to set the prefix with
>     --prefix=/usr/local/gcj and then do "make install" to install gcj in
>     the correct place.
>
>     I'm sure that's in the instructions.
>
>
> As part of GCC, gcj "should" from in any location, however, even if 
> you move it after installation. If this path is hardcoded then I'd say 
> that's a bug.
>
> Bryce
>
Here's what caused me to do what I did:

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've recompiled (21 hours) using the --prefix parameter and compilation 
has completed; I've run the test suite - same result as before: 6 errors.

I'm waiting for a blessing to proceed with just  "make install" in Bug 
42409 as I read the above strong recommendation with great deference and 
really do not want to affect my existing GCC.

John L. Poole