>>>>> On Mon, 17 Jul 2017 10:56:55 -0400, Phil Stracchino said: > > On 07/10/17 12:27, Phil Stracchino wrote: > > Actually, I think I *MAY* have solved this with the following set of > > counterintuitive configure options: > > > > --enable-client-only --enable-build-stored --disable-build-dird > > > > I note that --enable-client-only --enable-build-stored WITHOUT > > --disable-build-dird results in also building the dird. > > > OK, Bacula 9.0.1 configured this way on Solaris 11.3 says: > > client-only: yes > build-dird: no > build-stored: yes > > Which is what I wanted. But although it says it will build the stored, > it doesn't actually do so. There doesn't seem to be a way to build the > stored without also building the tools. But I don't actually want to > build the stored tools, because then I have to install a DB (or at least > the DB client libraries). > > It's just an opinion, but IMO there really ought to be a way to build a > stored without the stored tools, if you really don't want or need the > tools on that server.
As a workaround, you can install sqlite3 in some temporary location and use --with-sqlite3=... to point to it. The bacula-sd itself will not depend on sqlite3. __Martin ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
