Re: [Cp-tools-discuss] packaging cp-tools for debian

[Brian Jones]

Alex Lancaster <address@hidden> writes:

> >>>>> "GP" == Grzegorz Prokopski <address@hidden> writes:
> 
> GP> Hello!  It is a bit longer story (see
> GP> http://bugs.debian.org/156407 ) but I'd like to package cp-tools
> GP> part of cp-tools: javah, javap and serialver.  I see I will have
> GP> to also package kawa - let it be (ah - those neverending
> GP> dependencies ;-)
> 
> GP> For tests I fetched kawa-1.6.99.jar and while I am trying to
> GP> compile (using jikes + gnu classpath + kawa.jar as classpath) I am
> GP> getting:
> 
> GP> Is anyone maintaining this code? Can I count on that it will be
> GP> fixed in resonable time? (I ask because it seems that last change
> GP> to *.java files I am intersted in - was done 9 months ago)
> 
> Brian Jones is the author of those classes (and is also one of the
> project admins for Classpath proper), and I think he's subscribed to
> this list, so hopefully he'll have an answer for you.

gnu.bytecode is the only part of kawa used for the javap/javah stuff.
The reason I wrote the code was to more closely follow Sun's output
than the output of Kawa's "dump" utility.  That said, I gave up on
getting the actual bytecode (java assembly) to look exactly the same
due to the way gnu.bytecode generates that information being somewhat
difficult to interface with.

At the time, 1.6.95 I think, the code should have compiled cleanly.  I
did submit a couple of patches and they were included if I remember
correctly.  As Nic said I'm away right now and can't fix this for you
until the latter part of Sept.

It sounds like some method names may have changed, so it should be
easy to find via ChangLog or something.  My last update of my kawa
tree shows the last ChangLog entry on 07-18-2001.  I'd suggest a `cvs
update -D 20020718' or something like that.  With my tree I have no
compile problems.

I'd like to get Nic's help to get cp-tools linked to classpath's cvs
and get gnu.bytecode part of kawa imported as foreign sources we'll
update to stable versions as needed later.  In the future I want to
begin releasing cp-tools with classpath since it is just a part of
classpath.  Separate build is good since we need some sort of
"tools.jar" and maybe some shell scripts that assume a JVM called
"java" as an option.

This reminds me, where are we at with getting gjdoc stuff up on
gnu.org?  Does it work with gcj/gij now?

Brian
-- 
Brian Jones <address@hidden>