Michael Stapelberg wrote: >> If it is only a warning, then I would try compiling the code without your >> patch (i.e. ignore the warning), run the FD and periodically over a few >> weeks >> or months do a status client and look at the output of the following line: >> Heap: heap=901,120 smbytes=8,924 max_bytes=514,665 bufs=57 max_bufs=200 > OK, I will have an eye on that as soon as I have generated the inst-package > and running it productively. > >> The other solution is to find a GNU C++ compiler version 3.4 or later -- >> that >> should resolve the problem, but I imagine that is a painful solution ... > Yes. I think the MIPSpro we have here does optimize a lot better for the MIPS > architecture than the gcc. Also, my system administrator doesn't like GNU > software at all :-). > > Thanks for your mails and for helping to eliminate the problems. I really > appreciate it.
One other quick comment - once you get things compiled, you might want to look at running the regression suite to make sure that it's all working as expected: http://bacula.org/en/developers/Bacula_Regression_Testing.html -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
