Build Failure of WITH_LIBS3

Issue #6 resolved
Dominique Leuenberger created an issue

Enabling LIBS3 support results in a build failure with the 0.8.0 release:

[ 100s] Compiling build/oris3/oris3.cc [ 100s] In file included from build/oris3/s3backup.cc:8:0: [ 100s] public/ori/backup.h:93:13: error: 'unordered_map' in namespace 'std::tr1' does not name a type [ 100s] typedef std::tr1::unordered_map<std::string, bool> HasKeyCache; [ 100s] ^ [ 100s] public/ori/backup.h:94:5: error: 'HasKeyCache' does not name a type [ 100s] HasKeyCache hasKeyCache; [ 100s] ^ [ 100s] public/ori/backup.h: In member function 'bool BackupService::hasKey(const string&)': [ 100s] public/ori/backup.h:60:9: error: 'HasKeyCache' has not been declared [ 100s] HasKeyCache::iterator it = hasKeyCache.find(key); [ 100s] ^ [ 100s] public/ori/backup.h:60:31: error: expected ';' before 'it' [ 100s] HasKeyCache::iterator it = hasKeyCache.find(key); [ 100s] ^ [ 100s] public/ori/backup.h:61:13: error: 'it' was not declared in this scope [ 100s] if (it != hasKeyCache.end()) { [ 100s] ^ [ 100s] public/ori/backup.h:61:19: error: 'hasKeyCache' was not declared in this scope [ 100s] if (it != hasKeyCache.end()) { [ 100s] ^ [ 100s] public/ori/backup.h:66:9: error: 'hasKeyCache' was not declared in this scope [ 100s] hasKeyCache[key] = hk; [ 100s] ^ [ 100s] In file included from /usr/include/c++/4.8/tr1/memory:50:0, [ 100s] from build/oris3/s3backup.h:5, [ 100s] from build/oris3/s3backup.cc:11: [ 100s] /usr/include/c++/4.8/tr1/shared_ptr.h: At global scope: [ 100s] /usr/include/c++/4.8/tr1/shared_ptr.h:62:9: error: redefinition of 'class boost::bad_weak_ptr'

Comments (4)

  1. Ali Mashtizadeh

    This code has probably bit rotted as we're not officially supporting it for now. I'll look into it after the next release or I'd be happy to accept patches. If you have multiple computer it's not really necessary to backup onto S3.

  2. Ali Mashtizadeh

    Build is fixed, but the tool remains experimental as it was really a test. Unless someone picks it up and wants to maintain it I will cut it out of a future release entirely.

  3. Log in to comment