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

LP:712714 - handlersocket does not properly detect MariaDB version

Details

    • Bug
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      The handlersocket configure script does not properly detect the version of the mariadb source code. So, it reports that the versions of the mariadb source and the mariadb binary distribution differ and terminates. I am filing this as a MariaDB bug since it seems to me that it is in MariaDB's interest to provide a patch for handlersocket.

      To reproduce, follow the instructions for building handlersocket located at

      https://github.com/ahiguti/HandlerSocket-Plugin-for-MySQL/blob/master/docs-en/installation.en.txt

      for example, use the following configure:

      ./configure --with-mysql-source=/home/philips/bzr/mysql-5.3.0-MariaDB-alpha --with-mysql-bindir=/home/philips/bzr/maria-5.3-bintar/bin/

      and you will get the following error:

      checking mysql source... yes: Using /home/philips/bzr/mysql-5.3.0-MariaDB-alpha, version
      checking mysql binary... yes: Using /home/philips/bzr/maria-5.3-bintar/bin/mysql_config, version 5.3.0-MariaDB-alpha
      configure: error: MySQL source version does not match MySQL binary version

      Grep the configure script for the error message to see how version detection is implemented. See

      http://www.mysqlfanboy.com/2010/12/installing-handlersocket-nosql-plugin-into-miariadb-on-centos-5-5/

      for a possible patch.

      Attachments

        Activity

          People

            Unassigned Unassigned
            philipstoev Philip Stoev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 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.