Malcolm,
On 2006 May 26 , at 17.47, Malcolm J. Currie wrote:
>> This rings a vague bell, but I can't remember what's too old with
>> 1.3.1. How did it complain?
>
> Not sure what you meant by "it".
I was thinking of the Starlink autoconf system, but ...
> Trying to configure openjade
> the response is:
>
> ./configure --prefix=/usr/local/openjade-1.3.2
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... no
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking location of OpenSP include files... checking for
> /usr/local/openjade-1.3.2/include/OpenSP... no
> checking for /usr/local/include/OpenSP... no
> checking for /usr/include/OpenSP... no
> configure: error: "OpenSP include files do not exist"
OpenSP is the SGML parsing library that OpenJade depends on, also
from openjade.sourceforge.net. I think it was distributed alongside
openjade at one time, but now it looks like it's a separate
download. I think you'd have to install OpenSP in the place where
you plan to install openjade (ie, same prefix), and only after that
configure openjade.
> If you meant the 1.3.1 not being adequate, here's what
> configure said:
>
> According to ./configure, this component cannot be built:
> Your openjade is version 1 3 1 ; need 1.3.2 or better
Yes, that's what I was thinking of in fact. There was some bug
hidden in my SGML->TeX script which caused 1.3.1 to fail, but not
1.3.2, and which I never really had the opportunity to narrow down,
however desirable that would have been.
See you,
Norman
--
------------------------------------------------------------------------
----
Norman Gray / http://nxg.me.uk
eurovotech.org / University of Leicester, UK
|