On 02/16/2011 03:42 PM, Markus Hoenicka wrote:
> Hi Peter,
>
> Peter Czanik <cza...@balabit.hu> 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).
Well, the Makefile only complained about the missing openjade, I did not
install anything else. I guess, I better wait for you here, as I don't
know these tools at all...
> 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?
No. These were parts of the default Linux desktop install about 7+ years
ago :-)
>
>> 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<---
Problem solved:
fb81clean# diff test_mysql.sh.old test_mysql.sh
40c40
< mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force
--skip-name-resolve --user=${ME}
---
> mysql_install_db --basedir=/usr/local/ --no-defaults
--datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
Maybe some logic could be added to set "--basedir=" once
"mysql_install_db" is found.
> The sqlite3-specific output of the test looks fine to me.
And with the above fix the mysql tests also run successfully.
==================
All 2 tests passed
==================
>
>> 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.
SuSE is my main desktop system, and I tend to use FreeBSD on servers.
And I was just asked to do some tests on Debian 6.0...
My first syslog-ng tests succeeded, sqlite3 and mysql 5.5 seem to work
OK. I'll do more tests tomorrow and add postresql to the pool, as my
colleagues reported some more problems internally which I want to verify
both with the 0.8.3 release and with the CVS version.
Bye,
--
Peter Czanik (CzP) <cza...@balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
libdbi-devel mailing list
libdbi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-devel
