I may have asked this question before, but has anyone had any luck with
getting Bacula to utilize a hardware crypto accelerator for FD
encryption? Setting the engine(3) options in openssl.cnf do not appear
to have any affect. This can be confirmed with statistic programs which
hook into the c
On Wed, Sep 09, 2009 at 06:31:06AM -0700, wvoice wrote:
> Thanks Graham! So is newinstaller deprecated?
I don't know.
> You're right, I made the changes to ../win32_installer/Makefile and re-tried
> make from ../src/win32. After commenting out the document section of
> win32_installer/Makefile, i
:) You're a good man Graham! That's what I've done too.
Now I just need to fix NSIS to complete things.
Graham Keeling wrote:
>
> On Wed, Sep 09, 2009 at 06:19:47AM -0700, wvoice wrote:
>>
>> I'm actually trying to figure where things are breaking. I ran make in
>> ../src/win32/. Then I gre
Thanks Graham! So is newinstaller deprecated?
You're right, I made the changes to ../win32_installer/Makefile and re-tried
make from ../src/win32. After commenting out the document section of
win32_installer/Makefile, it craps out on the NSIS:
\n= Make of scripts succeeded =\n\n
make[1]:
On Wed, Sep 09, 2009 at 06:19:47AM -0700, wvoice wrote:
>
> I'm actually trying to figure where things are breaking. I ran make in
> ../src/win32/. Then I grep'd for bacula.pdf to see what was trying to build
> it. That's originally what took me to newinstaller. But the same happens for
> win32_in
I'm actually trying to figure where things are breaking. I ran make in
../src/win32/. Then I grep'd for bacula.pdf to see what was trying to build
it. That's originally what took me to newinstaller. But the same happens for
win32_installer as well.
Here's the output of the top level make in ../sr
On Wed, Sep 09, 2009 at 06:05:01AM -0700, wvoice wrote:
> And as far as running the commands, I did run ../src/win32/make for the
> 32-bit version.
Are you standing in the src/win32 directory when you type 'make'?
--
Le
Funny Kern, but if you re-read your README.mingw file, there is no mention of
win32_installer, newinstaller, etc. Nothing in the doc says one is used and
the other is deprecated.
The directions say to download and unpack a document tarball in the top
level source directory, which is a lot of fun
> On Wed, 9 Sep 2009 08:16:46 +0200, Kern Sibbald said:
>
> On Tuesday 08 September 2009 21:49:51 lorenz schori wrote:
> > Hi
> >
> > On 08.09.2009, at 20:50, Martin Simmons wrote:
> > >> On Tue, 8 Sep 2009 17:38:01 +0200, Kern Sibbald said:
> > >>
> > >> On Tuesday 08 September 2009 17:04
On Wednesday 09 September 2009 03:19:03 wvoice wrote:
> Hi Graham,
>
> That definitely solved that problem. I feel as if I'm in the home stretch
> now.
>
> Now I've got a couple of annoying issues remaining, but all of the .exe and
> .dll files are being built.
>
> Things are now bailing on the fin
On Tue, Sep 08, 2009 at 06:19:03PM -0700, wvoice wrote:
> Things are now bailing on the final Makefile in ../newinstaller/Makefile.
As I undestand it (looking at bacula-3.0.2), it doesn't use things in the
newinstaller directory.
It uses things in the win32_installer directory.
I stand in src/win
11 matches
Mail list logo
