Previous versions of Bacula have always depended on checking the static 
libraries for MySQL and PostgreSQL for certain symbols (multi-thread enabled, 
batch insert functionality, ...).

Recently various distributions have stopped releasing the static libraries, 
which make such detection fail.  In bacula-5.0.3, we attempted to fix this 
for PostgreSQL by adding explicit ./configure detection of certain entry 
points in the shared objects.  

The first version of this code released in 5.0.3 had a flaw, which I noticed 
after 5.0.3 was released, when I was building Bacula Enterprise binaries on a 
number of systems.  I fixed it, and back ported it to Branch-5.0, which is in 
the Source Forge repository.  So, in principle, this problem is resolved for 
PostgreSQL if you pull the code from the repository.

For MySQL, we still rely on the static libraries being present, and that works 
on all the machines that we support, as far as I am aware (E.g. RHEL 5.5, 
SLES 11, ...).  Apparently, RHEL 6.0 no longer has those static libraries for 
MySQL, so in the near future we will produce a fix for ./configure for MySQL 
to resolve this problem.

Best regards,

Kern

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to