From: Andrew John Hughes <a.hughes@dcs.shef.ac.uk>
To: Mark Wielaard <mark@klomp.org>
Cc: tromey@redhat.com, Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: Re: new module
Date: Wed, 21 Jun 2006 08:45:00 -0000 [thread overview]
Message-ID: <9BDBA329-C8C7-4D7C-8D3E-AE58D2D3524B@dcs.shef.ac.uk> (raw)
In-Reply-To: <1150876346.4407.7.camel@localhost.localdomain>
On 21 Jun 2006, at 08:52, Mark Wielaard wrote:
> On Mon, 2006-06-19 at 18:03 +0100, Andrew John Hughes wrote:
>> On Mon, 2006-06-19 at 10:00 -0600, Tom Tromey wrote:
>>> I added a new 'builder' module to mauve.
>>> This has the scripts we use on builder.classpath.org to drive the
>>> nightly builds.
>>>
>>> builder isn't yet set up to use this code, but hopefully I'll be
>>> doing that a bit later. First I wanted to clean up a few things in
>>> the scripts.
>>>
>>> Tom
>>
>> Great news! Particularly take a look at ecj, which still seems to be
>> failing, despite me pointing it at our built version in two different
>> ways... :(
>
> Yes, thanks a lot Tom!
> I saw Tom added a patch for real gcjx removal in the builder module. I
> have installed that patch now on builder.classpath.org and will
> monitor
> a full build cycle. It seems we were using the gcjx build a lot still
> even though I disabled it (in a crappy way, now that I see all the
> places Tom needed to patch, sorry about that). If things go right this
> should get our ecj-bootstrap back.
>
> Cheers,
>
> Mark
Hallelujah! We might finally see the result of Tom's concurrency patch.
--
Andrew :)
Postgraduate Student
Verification and Testing Group
Department of Computer Science
University of Sheffield
next prev parent reply other threads:[~2006-06-21 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 16:03 Tom Tromey
2006-06-19 17:03 ` Andrew John Hughes
2006-06-21 7:52 ` Mark Wielaard
2006-06-21 8:45 ` Andrew John Hughes [this message]
2006-06-21 10:54 ` Mark Wielaard
2006-06-21 11:36 ` Jeroen Frijters
2006-06-21 18:50 ` Andrew John Hughes
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=9BDBA329-C8C7-4D7C-8D3E-AE58D2D3524B@dcs.shef.ac.uk \
--to=a.hughes@dcs.shef.ac.uk \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=tromey@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).