[Box Backup-dev] Compile BoxBackup under Debian Woody failed

[Ben Summers]

On 21 Jun 2006, at 23:50, Martin Ebourne wrote:

> On Thu, 2006-06-22 at 00:32 +0200, Roy wrote:
>> I'm getting an error when compiling:
>> Daemon.cpp: In method `int Daemon::Main(const char *, int, const  
>> char **)':
>> Daemon.cpp:174: initialization of non-const reference type `class
>> auto_ptr<Configuration> &'
>> Daemon.cpp:174: from rvalue of type `auto_ptr<Configuration>'
>> /usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/ 
>> memory:40:
>> in passing argument 1 of `auto_ptr<Configuration>::operator
>> =(auto_ptr<Configuration> &)'
>> make[2]: *** [../../release/lib/server/Daemon.o] Error 1
>> make[2]: Leaving directory `/root/boxbackup-0.10/lib/server'
>> make[1]: *** [dep_modules] Error 2
>> make[1]: Leaving directory `/root/boxbackup-0.10/bin/bbackupd'
>> make: *** [parcels/boxbackup-0.10-backup-client-linux-gnu.tgz]  
>> Error 2
>>
>> Don't know what to do right now. I think a good night sleep will  
>> help ;-)
>
> Upgrade. :)
>
> You already mentioned that you've only got g++ 2.95. That is ancient,
> and not remotely ISO C++ conformant, and therefore Box doesn't compile
> properly on it. Look through the archives if you like, this was  
> covered
> a while ago. Don't know if anyone ever managed to hack it through, I
> think they took to building a more recent g++.

I did have it compiling under 2.95, but that was an earlier version  
and maybe the code has changed. But not that line.

My recollection of the 2.95 problem was that it was using the 3.x  
libraries, and getting upset.

One way of avoiding this problem might be to mount the filesystems  
via NFS on another machine, and run an instance of bbackupd on that.  
Use the SyncAllowScript to check for the mount actually working,  
otherwise bbackupd will delete everything on the server. This  
approach is NOT RECOMMENDED, but may work if you really can't compile  
it or upgrade the machine and follow the advice about the  
SyncAllowScript.

Ben