Re: [libdbi-devel] next release

[Markus H. <mar...@mh...>]

Hi Peter,

Peter Czanik <cz...@ba...> was heard to say:

> I started testing on FreeBSD 8.1 (the current long term support
> release). I checked out the latest cvs version for libdbi and libdbi
> drivers.
>

That's good as this is my main platform as well. This should make it  
easier for me to reproduce any problems that you run into.

> Libdbi: it only compiles if was configured with --disable-docs. Without
> this option, if openjade is missing, it fails because of that, if it's
> there, it still fails, because openjade does not like the document.
>

Bootstrapping from a cvs checkout is a bit trickier than building from  
a tarball. We decided back then to ship the PDFs and HTMLs along with  
the DocBook sources, so the end-user should never need to build the  
docs. I'll see if I can build the docs on 8.1, but I can't recall ever  
having problems with this as long as the SGML toolchain is complete  
(including DocBook DSSSL stylesheets, an appropriate CATALOG file, and  
a proper $SGML_CATALOG_FILES). SGML is darn old-fashioned, but I  
hesitate to convert the docs to XML. You'd require Java and FOP to  
build PDFs then, besides XSL stylesheets and xsltproc. We could as  
well drop PDFs altogether and build only HTML docs with xsltproc. I'm  
open to suggestions here. Are xsltproc and the DocBook XSL stylesheets  
likely to be installed on a run-of-the-mill computer these days?

> Libdbi-drivers has the same problem with openjade. I compiled it with
> sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my
> primary db platform). Compilation/installation went fine, but running
> "make check" failed. Should I send the output of "make check" here (it's
> quite long...), or only privately?
>

Below is the cause of the failure. Joao, are you listening? This looks  
like a cgreen problem to me. Is it necessary to install cgreen  
separately in order to make this work? Could you please look into this?

--8<---
FATAL ERROR: Could not find ./bin/my_print_defaults

If you compiled from source, you need to run 'make install' to
copy the software into the correct location ready for operation.

If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.
--8<---

The sqlite3-specific output of the test looks fine to me.

> it compiled OK. And I'll also check it on Linux (openSUSE 11.4 RC1)
>

Much appreciated as I don't have a SuSE system around here.

regards,
Markus



-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38