[Box Backup] Could do with some advice on getting Boxbackup compiled ....

[boxbackup@fluffy.co.uk]

Thanks for that Martin.

I've managed to get past most of the problems by installing up-to-date compilers etc.
wherever possible.

However, 'make' still bombs out.  Here's the last bit of the output .....
=============================================

(cd bin/bbackupquery; make RELEASE=1)
make[1]: Entering directory `/downloads/boxbackup-0.10/bin/bbackupquery'
g++ -DNDEBUG -O2 -Wall -I../../lib/common -I../../lib/compress -I../../lib/crypto
-I../../lib/server -I../../lib/backupclient  -DBOX_VERSION="\"0.10\"" 
-I/usr/local/BerkeleyDB.4.4/include -I/opt/openssl-0.9.8a/include -g -Wall -c
BackupQueries.cpp -o ../../release/bin/bbackupquery/BackupQueries.o
BackupQueries.cpp: In member function `void
   BackupQueries::CommandGetObject(const std::vector<std::string,
   std::allocator<std::string> >&, const bool*)':
BackupQueries.cpp:818: `LLONG_MIN' undeclared (first use this function)
BackupQueries.cpp:818: (Each undeclared identifier is reported only once for
   each function it appears in.)
BackupQueries.cpp:818: `LLONG_MAX' undeclared (first use this function)
make[1]: *** [../../release/bin/bbackupquery/BackupQueries.o] Error 1
make[1]: Leaving directory `/downloads/boxbackup-0.10/bin/bbackupquery'
make: *** [parcels/boxbackup-0.10-backup-client-linux-gnu.tgz] Error 2

=============================================

Any idea how to fix this?

I feel I have to persevere a little longer as I'll end up with a mixed network of
RH7.3 and CentOS systems - can't be avoided, I'm afraid.  The Boxbackup server will
be a CentOS box, but most of the production servers will be RH7.3 for the forseeable
future (if it ain't broke, don't fix it principle, I'm afraid).

Regards,

Dave

Quoting Martin Ebourne <lists@ebourne.me.uk>:

> dave_d@boltblue.com wrote:
> > ...
> > So ....  SME server is basically a stripped down RH7.3 system in its  
> >  present release,
> > soon to become a stripped down CentOS 4.2 (2.6.x kernel) in the next  
> >  release.
> > ...
> > #./configure --with-ssl-headers=/opt/openssl-0.9.8a/include
> > --with-ssl-lib=/opt/openssl-0.9.8a/lib  --enable-static-bin
> > --prefix=/usr/local/bin/boxbackup --enable-gnu-readline
> 
> --enable-static-bin is not guaranteed to work, and is only  
> semi-supported at the moment. I recommend you don't use it unless  
> really necessary. If you do then post any bugs you get with it to the  
> -devel list and we'll try to work through them. However, this is not  
> your problem at the moment.
> 
> > Daemon.cpp: In method `int Daemon::Main (const char *, int, const char
> > **)':
> > Daemon.cpp:174: no match for `auto_ptr<Configuration> & =
> > auto_ptr<Configuration>'
> > /usr/include/g++-3/memory:40: candidates are: auto_ptr<_Tp>
> > &auto_ptr<_Tp>::operator= (auto_ptr<_Tp> &) [with _Tp = Configuration]
> > /usr/include/g++-3/memory:48:                 auto_ptr<_Tp>
> > &auto_ptr<_Tp>::operator= (auto_ptr<_Tp1> &) [with _Tp1 =
> > Configuration, _Tp = Configuration]
> > ...
> > As far as I can make out, auto_ptr is part of the C++ STL.  Not being a C++
> > programmer puts me at a bit of a disadvantage here, but I would have  
> >  thought that
> > 'auto_ptr' was included as part of the gcc package.
> 
> This is due to an old version of GCC. The interface to auto_ptr that  
> was standardised is significantly different to the version that a lot  
> of old compilers had while the C++ standardisation was still in  
> progress.
> 
> This error has been discussed before, but no-one has provided a  
> suitable patch to work around it, and I'm not sure how far we want to  
> go supporting old non-standards conforming compilers. The good news is  
> that when you switch to CentOS 4.2 you'll be using a modern compiler  
> and it will just work.
> 
> Cheers,
> 
> Martin.
> _______________________________________________
> boxbackup mailing list
> boxbackup@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
> 


--------------------------------------------------------------
Sent with "Me-Mail", Boltblue's FREE mobile messaging service.
http://www.boltblue.com