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

cmake fails to detect boost libraries

    XMLWordPrintable

Details

    • 10.0.20

    Description

      When building MariaDB 10.0.19 (as well as 10.0.17, 10.0.18 and possibly earlier) cmake fails to pick up the installed boost libraries.

      # cmake . -LAH
      -- Running cmake version 3.1.3
      -- MariaDB 10.0.19
      -- Packaging as: mariadb-10.0.19-FreeBSD10.1-x86_64
      getconf: no such configuration parameter `LEVEL1_DCACHE_LINESIZE'
      -- suffixes <.so;.a>
      -- OPENSSL_INCLUDE_DIR = /usr/local/include
      -- OPENSSL_LIBRARIES = /usr/local/lib/libssl.so
      -- CRYPTO_LIBRARY = /usr/local/lib/libcrypto.so
      -- OPENSSL_MAJOR_VERSION = 1
      -- SSL_LIBRARIES = /usr/local/lib/libssl.so;/usr/local/lib/libcrypto.so
      -- Configuring OQGraph
      -- Boost version: 1.55.0
      -- Requisites for OQGraph not met. OQGraph will not be compiled

      When I add LDFLAGS and CXXFLAGS cmake starts detecting Boost OK and reports Requisites for OQGraph are OK but then fails to compile storage/perfschema/pfs.cc

      /usr/ports/databases/mariadb100-server/work/mariadb-10.0.19/storage/perfschema/pfs.cc:5285:3: error: cannot initialize
             a member subobject of type 'digest_add_token_v1_t' (aka 'struct PSI_digest_locker *(*)(struct PSI_digest_locker
             *, uint, struct OPAQUE_LEX_YYSTYPE *)') with an lvalue of type 'void (PSI_digest_locker *, const
             sql_digest_storage *)': different number of parameters (3 vs 2)
         pfs_digest_end_v1,

      Attachments

        Activity

          People

            serg Sergei Golubchik
            spil Bernard Spil
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.