public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: ronis@ronispc.chem.mcgill.ca
Cc: GCC <java@gcc.gnu.org>
Subject: Re: Bootstrap failure in 4.4.1
Date: Fri, 24 Jul 2009 08:41:00 -0000	[thread overview]
Message-ID: <4A69739C.5020403@redhat.com> (raw)
In-Reply-To: <1248366663.14628.14.camel@ronispc.chem.mcgill.ca>

On 07/23/2009 06:31 PM, David Ronis wrote:
> gjar is in /usr/bin, and gives:
> 
> gjar --version
> jar (GNU Classpath) 0.98
> 
> Isn't this built as part of gcc?  It has a similar timestamp as my
> installed 4.4.0 gcc.

Right: I think that's the one that is crashing.

> Finally, shouldn't a bootstrap build use its own gjar?

No.  it's the just-built jar, and it hasn't been tested yet, and it
might not even be for the same architecture as the host machine.

> One seems to have been built:
> 
> find -name gjar -ls
> 3503030    4 -rwxr-xr-x   1 ronis    ronis        2048 Jul 22
> 23:57 ./i686-pc-linux-gnu/libjava/classpath/tools/gjar
> 
> On the other hand, trying to run this version gives:
> 
>  ./gjar --version
> ./gjar: line 48: /usr/share/classpath/tools.zip: No such file or
> directory
> ./gjar: line 48: exec: /usr/share/classpath/tools.zip: cannot execute:
> No such file or directory
> 
> (In fact, there is no /usr/share/classpath directory).

It's not installed yet.  If you don't have a working gjar it should be
possible to use zip to create the archive.  But I would have expected
that you should be able to use your distro's gjar.  if this crashing
program *is* your distro's gjar, then that's another problem.

Andrew.

      reply	other threads:[~2009-07-24  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1248365867.14628.7.camel@ronispc.chem.mcgill.ca>
2009-07-23 16:20 ` Andrew Haley
2009-07-23 16:31   ` David Ronis
2009-07-24  8:41     ` Andrew Haley [this message]

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=4A69739C.5020403@redhat.com \
    --to=aph@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=ronis@ronispc.chem.mcgill.ca \
    /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).