On 20.12.18 10:07, Kern Sibbald wrote: > Hello Sven, > > Sorry you had problems. > > On my system, once libs3 is installed on the system, building Bacula > automatically picks it up.
Does it? Looking really really hard at the shell code in configure tells me: It doesn't. This line https://bacula.org/git/cgit.cgi/bacula/tree/bacula/configure?h=Branch-9.4#n27135 always evaluates to false and then the whole section until https://bacula.org/git/cgit.cgi/bacula/tree/bacula/configure?h=Branch-9.4#n27234 is skipped, disabling S3 support. The cloud-driver will still be compiled, but without the S3 backend and just the (dummy?) File backend in place. Once you just add "support_s3=yes", for example in this block here https://bacula.org/git/cgit.cgi/bacula/tree/bacula/configure?h=Branch-9.4#n21810 (or apply my patch to configure.in and rerun aclocal) you will get the same error as me, missing "authRegion", because that code was only added to libs3 in November 2016. > Yes the original libs3 package is a bit old as the author stopped > updating it. > > I am reasonably sure I am building and running on Ubuntu 18.04 and using > the installed packages libs3-2 and libs3-dev. dpkg says that it is > version 2.0-3 Ubuntu just imports the version from Debian and does nothing special. > In the mean time, I hope that our rpm/debs packager will release some > binaries. I am trying to get the official Debian packages ready for Debian Buster, together with Carsten Leonhardt, so upstream binaries won't help much other than as an inspiration. Grüße, Sven.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
