On 08/20/2017 12:36 AM, Per Jessen wrote:
Marc Chamberlin wrote:
Thanks Per, well I think you might have put me on the right track, nice to see it done through a fresh set of eyes! I had been using the default config file (with modified paths that suited my environment) that Bacula supplies in their example directory, that their installation instructions recommended. Within that config file there were two options -
--enable-static-tools \ --disable-libtool \
and on a hunch, after seeing how you had successfully built Bacula, I decided to remove these two options. And it worked! (at least it compiles OK) I don't grok what these options do exactly, or why Bacula recommends using them, A wild guess - they enable the building of static versions, i.e. monolithic blobs that you can run anywhere because they don't depend on loading any local libraries. For a backup tool, that's not a bad idea.
I was simply doing my best to follow their recommended procedures. (blind monkey doing what told!) With these options, it appears that their makefile wants to compile mysql. possibly the same reasoning - to get object code for building static versions.
You know, I like your thinking/reasoning Pers... For now I think I will just try and get Bacula running without these options, but for putting it back in the openSuSE repos later, and supporting it for openSuSE, I may want to revisit this issue and figure out how to get it working with mysql built in.. I will ask on the Bacula forums about it and what they recommend when I get that far... Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org