public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: jlpoole@pon.net
Cc: java@gcc.gnu.org
Subject: Re: GCCMain not found & test suite errors fatal?
Date: Sun, 03 Jan 2010 18:31:00 -0000	[thread overview]
Message-ID: <4B40E279.3090601@redhat.com> (raw)
In-Reply-To: <4B40DE6F.1010003@pon.net>

On 01/03/2010 06:14 PM, John Poole wrote:
> On 1/3/2010 8:28 AM, Andrew Haley wrote:
>>
>> I'd try stracing gcj to find out what's going on
>>
>>   $ strace -f -etrace=file gcj -c HelloWorld.java
>>
>> This will tell you where gcj is looking for its jarfiles.  Look for
>> something like this:
>>
>> ...
>> 547   execve("/home/aph/gcc/trunk/install/libexec/gcc/x86_64-unknown-linux-gnu/4.5.0/ecj1", ["/home/aph/gcc/trunk/install/libe"..., "Hello.java", "-g1", "-fbootclasspath=./:/home/aph/gcc"..., "-g1", "-fsource=1.5", "-ftarget=1.5", "-fzip-dependency", "/tmp/ccXyDB9d.zip", "-fzip-target", "/tmp/ccipPqBc.jar"], [/* 42 vars */]) = 0
>> ...
>> 547   stat("/home/aph/gcc/trunk/install/share/java/ecj.jar", {st_mode=S_IFREG|0644, st_size=1377431, ...}) = 0
>> 547   open("/home/aph/gcc/trunk/install/share/java/ecj.jar", O_RDONLY) = 3

> Perfect.
> 
> I followed your suggestion; installed strace and reran the revised 
> command line.  The output can be referenced at http://pastebin.com/m7cb292d5
> 
> The definitive line is:
> 
> 172.  [pid  6423] access("/usr/local/share/java/ecj.jar", F_OK) = -1 
> ENOENT (No such file or directory)
> 
> See also lines 81,82 and 85.
> 
> Basically, the problem is that compiler was looking for ecj.jar under a 
> fixed(?) /usr/local/share path instead of the path where I had custom 
> installed: /usr/local/gcj;  moreover it should have been looking under 
> the full path of /usr/local/gcj/usr/local/share/java.

OK, so we need to know why that happened.  It might be a bug in gcj or
you might not have configured gcc correctly.  My guess is the latter,
but you never know.

Please look at the config.log in the top of the gcc build directory,
and cut-n-paste the configure line that's there.  I think I know
what's wrong, but I'll need to see it to be sure.

Andrew.

  reply	other threads:[~2010-01-03 18:31 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 [this message]
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
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=4B40E279.3090601@redhat.com \
    --to=aph@redhat.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).