[CCC DEV] Doh!

[Christian Jacobsen]

Hi,

If you are using a copy of trunk from the 12th of Feb then you are
using a quite old snapshot of trunk. You should either delete and
check out a new copy or run 'svn update' to get your copy up to date.
Also, it is probably easier to quote the revision # for subversion
working copies rather than dates, ie the trunk at the time of writing
is at 6393, which is what you need to get the kroc stuff to work.

In general when working with trunk you should probably always try to
be as up to date as possible.

I'll look into whether the CLASSLIB setting is something that we
should mention somewhere so we don't forget.

Cheers,
  Christian

On 3 March 2010 23:11, Dennis Meade <stone.misc at gmail.com> wrote:
>
>
> Christian,
>
> The Java problem was fixed by adding CLASSLIB pointing to the Java lib
> directories. I had to restore the machine I'm working on from scratch awhile
> ago and CLASSLIB was not re-entered. Apparently all the Java stuff I use can
> find the libs by other means.
>
> With regard to building KRoC, I'm using a copy of the build from
> http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/trunk last changed Fri
> Feb 12 12:55:53 EST 2010 by djs. Is this correct? I synced my working copy
> with trunk and KRoC still fails
>
> Dennis
>
> Christian Jacobsen wrote:
>>
>> Hi Dennis,
>>
>> I'm not currently sure about the Java errors. They look a bit odd...
>> It could well be due to my java autodetect script.
>>
>> Could you paste the output from starting msys, ie what JDK version was
>> found and paths?
>> Also type `which java` and paste in the output of that
>> If you could also type 'export' and paste in the output of that.
>> That may or may not shed light on things.
>>
>> The ./build_kroc.sh error is entirely my fault. I'd commented out a
>> line in the build script that takes a very long time on my vm while
>> developing. If you update your working copy you'll get correct version
>> of that script, and ./build_kroc.sh should now be able to find the
>> configure scripts.
>>
>> Thanks,
>>  Christian
>>
>
>
> _______________________________________________
> developers mailing list
> developers at concurrency.cc
> https://ssl.unhosting.org/mailman/listinfo/developers
>