public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Balkissoon <abalkiss@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: mauve-patches@sources.redhat.com
Subject: Re: new Harness with compilation capabilities
Date: Tue, 25 Apr 2006 15:58:00 -0000	[thread overview]
Message-ID: <1145980726.9046.26.camel@tony.toronto.redhat.com> (raw)
In-Reply-To: <20060425122051.GA5167@redhat.com>

I will look into this right away.

--Tony

On Tue, 2006-04-25 at 13:20 +0100, Gary Benson wrote:
> Anthony Balkissoon wrote:
> > This new version of the Harness has auto-compilation capabilities
> > and also fixes a lot of bugs and performance issues that were
> > present in the last one.
> 
> This looks really nice, but I can't get it to run.  I've applied the
> attached patch to make it build with 1.4 and I'm doing:
> 
>   ./configure --enable-auto-compile \
>       --with-classpath-install-dir=/home/users/gary/work/classpath/install \
>       --with-vm=jamvm
> 
> I then do:
> 
>   CLASSPATH=`pwd` make
> 
> (For some reason it doesn't find config.java without the extra bit).
> When I go to run some tests ecj is being invoked with -bootclasspath
> /home/users/gary/work/classpath/install/share/classpath and that
> directory contains the following:
> 
>   examples/  glibj.zip  README  tools/  tools.zip
> 
> Am I building Classpath in some wierd way?
> 
> Cheers,
> Gary

  reply	other threads:[~2006-04-25 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 20:23 Anthony Balkissoon
2006-04-24 20:29 ` Anthony Balkissoon
2006-04-25 12:21 ` Gary Benson
2006-04-25 15:58   ` Anthony Balkissoon [this message]
2006-04-25 16:15     ` new Harness with compilation capabilities (FIX inline) Anthony Balkissoon
2006-04-25 16:24       ` Anthony Balkissoon
2006-04-26  9:58         ` Gary Benson

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=1145980726.9046.26.camel@tony.toronto.redhat.com \
    --to=abalkiss@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=mauve-patches@sources.redhat.com \
    /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).