![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
Marc Chamberlin wrote:
And on investigation I discovered that Bacula's build process wants all the source .c files for mysql and it is indeed trying to compile them as part of the build process for Bacula. I too was surprised by this. The -devel packages alone are insufficient, and in fact the Bacula documentation says that I have to download the source code files for mysql, install them somewhere, and then tell the Bacula config where they were installed. I don't want the source code to be inconsistent with what openSuSE installs for mariadb so I am trying to install the source files in the YaST/zypper way.
I wouldn't bother with that, it's just source code. Just put it where your build can get to it.
Question - If I have to build mariadb from source, is there documentation/instructions on how to do so for Leap42.3?
It's likely the usual way - untar, configure, make. Nothing special required I would think.
I am not sure where you are headed though, are you saying that mariadb/mysql was built using autotools?
Almost certainly. Most things are. -- Per Jessen, Zürich (17.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org