[MKSearch-dev] Week 4 round up

[Bruno Postle]

On Thu 11-Nov-2004 at 18:59 -0000, Phil Shaw wrote:
>
> Welcome back, thanks for the comments. We were in Rome in August and 
> had a great time, though fairly weary after cramming it all into two 
> days. Baking hot at that time of year, I imagine it was more 
> comfortable for you.

It was a nice 20-25°.  We were there for seven nights and took it 
easy as Robyn is pregnant - So we didn't actually see very much but 
had a relaxing time.

> I had all sorts of bizarre Subversion problems and couldn't work out 
> why, now the penny drops! I'm not sure how this directory came to be 
> under version control in the first place, I have removed it now.

It confused me for a while.  Though now that build isn't in 
subversion, these commands fail:

  mkdir $mk_build/jaxp

..it should probably be this:

  mkdir -p $mk_build/jaxp

>> So, the bash scripts could first test to see if $mk_build is set:

> Yes, fair point, I'll do that tomorrow.

The new test-environment.sh script does the job perfectly.

>> I get an error trying to compile jspider, this error is actually
>> generated by util/list-jspider.sh:

This is ok now.  In fact everything in the bin/ directory now builds 
properly though there is a typo at the top of compile-jaxp.sh:

  * the parser class implementations.

> >   ./run-jtidy.sh foo.html
> >   Tidy (vers 4th August 2000) Parsing "foo.html"
> >   Exception in thread "main" java.lang.IllegalAccessError
> >      at _Jv_SearchMethodInClass(java.lang.Class, java.lang.Class,
> >      _Jv_Utf8Const, _Jv_Utf8Const) (/usr/lib/libgcj.so.4.0.0) at
> >      _Jv_ResolvePoolEntry(java.lang.Class, int)
> >      (/usr/lib/libgcj.so.4.0.0) at
>
> This problem may originate from the runtime environment, hence the 
> shared object references: *.so.4.0.0. I presume the 4.0.0 reference 
> indicates your version of GCJ. I'm using version 3.3.3.

No the /usr/lib/libgcj.so.4.0.0 file is actually part of 
libgcj-3.3.2.  The '.so.4.0.0' numbering system is libtool's and 
allows multiple versions of a library to co-exist on a linux system, 
you can read all the gory details here:

  http://www.gnu.org/software/libtool/manual.html#SEC34

> There shouldn't be incompatibilities, but the GNU Java tools are 
> work in progress. Could you try making the JARs afresh on your own 
> system? 

> Then try again with JTidy.

I get the same error, both with html files in the current directory 
and when using absolute paths.

> If you're still having problems with this tomorrow, please let me 
> know and I'll put some time into it next week.

Presumably the problem is caused by file-handling and wouldn't be a 
problem when the library is used directly?

-- 
Bruno