public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: jlpoole@pon.net
Cc: Bryce McKinlay <bmckinlay@gmail.com>, java@gcc.gnu.org
Subject: Re: GCCMain not found & test suite errors fatal?
Date: Tue, 05 Jan 2010 10:17:00 -0000	[thread overview]
Message-ID: <4B4311A5.1020707@redhat.com> (raw)
In-Reply-To: <4B42A747.5080606@pon.net>

On 01/05/2010 02:43 AM, John Poole wrote:
> 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.

> 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.

All becomes clear.

I've never come across anyone using DESTDIR=path-to-rootdir before, which
is why I've never seen this bug.  The usual way is to configure with
--prefix=path-to-rootdir followed by "make install".

I'll have a look at fixing this.

Andrew.

  reply	other threads:[~2010-01-05 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31 17:17 John Poole
2010-01-03 16:28 ` Andrew Haley
2010-01-03 18:14   ` John Poole
2010-01-03 18:31     ` Andrew Haley
2010-01-03 18:45       ` John Poole
2010-01-03 19:00         ` Andrew Haley
     [not found]           ` <7230133d1001040328x4557cd0cn8eba6443e8c74616@mail.gmail.com>
2010-01-04 11:41             ` Andrew Haley
2010-01-05  2:43             ` John Poole
2010-01-05 10:17               ` Andrew Haley [this message]
2010-01-06 16:39                 ` RFD: Precompile ecj [Was Re: GCCMain not found & test suite errors fatal?] Andrew Haley
2010-01-06 17:01                   ` David Daney
2010-01-06 17:26                     ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2009-12-31 14:36 GCCMain not found & test suite errors fatal? John Poole
2009-12-31 14:49 ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B4311A5.1020707@redhat.com \
    --to=aph@redhat.com \
    --cc=bmckinlay@gmail.com \
    --cc=java@gcc.gnu.org \
    --cc=jlpoole@pon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).