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

forcing wolfssl with new cmake option -DWITH_WOLFSSL=ON

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Fix
    • N/A
    • Compiling
    • None

    Description

      dear developers,

      my debian siduction system have gnutls library by default included because of curl gnutls dependency, and i dont want gnutls compiling inside mariadb server compile.

      i want forcing wolfssl compiling with cmake option and cmake scripts checking with_openssl == gnutls and openssl and yassl already.. i want force directly wolfssl compiling.

      actual behavioar when i remove libgnutls.so librarys cmake spits me error..

      cmake: error while loading shared libraries: libgnutls.so.30: cannot open shared object file: No such file or directory

      cmake autodetects everytime gnutls

      – The following OPTIONAL packages have been found:

      • LIBAIO
      • Git
      • LibXml2
      • Boost (required version >= 1.40.0)
        Required for the OQGraph storage engine
      • Judy
        Required for the OQGraph storage engine
      • GSSAPI
      • BZip2
      • LZ4 (required version >= 1.6)
      • LibLZMA
      • LZO
      • Snappy
      • BISON (required version >= 2.4)

      – The following REQUIRED packages have been found:

      • Curses
      • URING
      • GnuTLS (required version >= 3.3.24)
      • CURL

      so moving files from lib directory to different directory before compiling not possible..

      thanks and best regards

      Attachments

        Activity

          People

            Unassigned Unassigned
            mariadbcomplain mariadbcomplain
            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.