results with jade 1.1.90

[apharris@xxxxxxxxxxxxxxxxxxx (Adam P. Harris)]

[ This is a bit off-topic of for this list, but James reported the
  experimental jade release here, so I'm CC'ing here also, for any who
  are using the pre-release of jade. ]

James, this is my report on your experimental pre-release of jade,
which reports itself as:

jade:I: Jade version "1.1.90"
jade:I: SP version "1.3.2"

I have found no problems introduced with this version.  My testing was
not extensive; I merely ran jade over a set of documents that I have.
Unlike previous releases, I did manage to compile jade with eg++,
namely egcs-2.91.57.  The shared library used for jade are:

> ldd /usr/bin/jade
	libsp.so.1 => /usr/lib/libsp.so.1 (0x40011000)
	libstdc++-libc6.0-1.so.2 => /usr/lib/libstdc++-libc6.0-1.so.2 (0x401fb000)
	libm.so.6 => /lib/libm.so.6 (0x4023e000)
	libc.so.6 => /lib/libc.so.6 (0x40259000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

As you can see, I also happen to have my own (unsupported) method of
building a shared libsp.  (Cees is working on this issue, using
libtool, as I know.  For now I'll continue to use my gcc/elf-specific
method.)

With respect to libsp, I do find that the libsp contained in your
release is actually incompatible with the older libsp.  For instance,
I have a dsc which links with libsp dynamically, but now it refuses to
run:

dsc: error in loading shared libraries
: undefined symbol: _vt.9EntityApp.9Messenger

I suppose this means that we should bump the major number on libsp so
that older and newer libsp's can co-exist?  I'm not completely clear
on the intricacies with SO numbering.

.....A. P. Harris...apharris@xxxxxxxxxxxxxx<URL:http://www.onShore.com/>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist