Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-19110

Cassandra plugin fails to build with libthrift-dev in Debian unstable

    XMLWordPrintable

Details

    Description

      Traditionally the Cassandra plugin has not been built in Debian as the Thrift library is not available there. Our own buildbot builders have had a manually installed Thrift library.

      Since recently however libthrift-dev has been introduced into Debian repositories:
      https://packages.debian.org/buster/libthrift-dev

      I tried to build latest 10.4 using it but the build fails with:

      }}
      boost::shared_ptr<org::apache::cassandra::CassandraIf>; _Alloc = std::allocator<boost::shared_ptr<org::apache::cassandra::CassandraIf> >]'
      /tmp/building/package/storage/cassandra/gen-cpp/Cassandra.h:5065:92:   required from here
      /usr/include/c++/8/ext/new_allocator.h:130:29: error: invalid application of 'sizeof' to incomplete type 'boost::shared_ptr<org::apache::cassandra::CassandraIf>'
             { return size_t(-1) / sizeof(_Tp); }
                                   ^~~~~~~~~~~
      make[4]: *** [storage/cassandra/CMakeFiles/cassandra.dir/build.make:76: storage/cassandra/CMakeFiles/cassandra.dir/cassandra_se.cc.o] Error 1
      make[4]: Leaving directory '/tmp/building/package/builddir'
      {{

      Full log at https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/149622

      Are these failures something that could be fixed so that we could start building the Cassandra plugin everywhere?

      Attachments

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.