W li=B6cie z czw, 17-10-2002, godz. 02:49, Etienne M. Gagnon pisze:=20
> Hi Grzegorz,
>=20
> I have made the 1.0.5 release, paying much attention to make as clean
> a build as possible (running all of the auto* stuff on a clean source
> tree). Can you check if you still get the Debian build problems with
> this version?
>=20
> If you still get these problems, then you'll have to tell me exactly
> about how you build your package. I guess I'll also have to learn
> about the Debian build procedures.
I already mailed Etienne the answer along with other mail, but just so
that everybody knew...
1.0.5 works well, the auto* build problems seem to be solved
the only problem is - you have to use jikes 1.15 (not 1.17)
1.0.5 supports 3 architectures: i386, alpha and ia64
As we're at multiarch support....
I'd like to see my one-for-all-arches patch integrated in some
further release (I hope Etienne hasn't change his mind).
But it won't make much sense if we're not able to test the beast.
I think seriously about some automated test suite that could give us
some results about how well sablevm works on every (wannabe)
supported arch. (We should hear soon if it really works on ia64)
It seems that nobody tested in on alpha so far (else - we'd already
have bugreports, because alpha port builded by autobuilders was
unusable due to problems with autotools usage in sablevm).
I am gonna ITP: sablevm-testsuite now.
For now it will consist of three tests:
- HelloWorld (should always work)
- TestAWT (doesn't work ATM)
- TestSwing (doesn't work ATM)
I already ITPed mauve test suite, but I don't think we really need
such big mechinery yet when there are very visible and well known bugs
(or rather missing features).
Hmm... I think I am gonna open a wine and celebrate 8)
Grzegorz B. Prokopski
|
