> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Does work with GNU make though. I must have just figured that Bacula was
> one of those packages that only worked with GNU -- good to see that it
> isn't (though I believe at present, it only builds with GCC -- am I
> right on that one?).
No.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Does work with GNU make though. I must have just figured that Bacula was
one of those packages that only worked with GNU -- good to see that it
isn't (though I believe at present, it only builds with GCC -- am I
right on that one?).
Kern Sibbald wrote
It is a problem on all platforms if you don't have any of the options.
Fixed in the current CVS.
>> On Tue, 17 Oct 2006 16:55:41 -0400, Ryan Novosielski said:
>>
>> this host, so this must have worked at some point... but I can't imagine
>> what could be different between then and now. I went
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Simmons wrote:
>> On Tue, 17 Oct 2006 16:55:41 -0400, Ryan Novosielski said:
>> this host, so this must have worked at some point... but I can't imagine
>> what could be different between then and now. I went back and tried
>> 'make install'
> On Tue, 17 Oct 2006 16:55:41 -0400, Ryan Novosielski said:
>
> this host, so this must have worked at some point... but I can't imagine
> what could be different between then and now. I went back and tried
> 'make install' on that version too, but it blows up the same way.
>
> At any rate,
Hi,
Without trying to analyze in detail, could it be that you are running make
in some unexpected environment? I have encountered similar problems (not
bacula specific) when I, for example, try to run a bash script from the
csh prompt.
- Sarath
On Tue, 17 Oct 2006, Ryan Novosielski wrote:
> ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The interesting thing is that I have Bacula 1.39.22 BETA installed on
this host, so this must have worked at some point... but I can't imagine
what could be different between then and now. I went back and tried
'make install' on that version too, but i
