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

OQGraph is missing from 5.5 bintars (and debs)

Details

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

    Description

      OQGraph in 5.3 needs boost 1.40 or later, otherwise it's not built.
      In 5.5 it needs boost 1.45.
      We have 1.42 on all our package-building VMs.

      As a result, all 5.5. binary packages don't have OQGraph.

      VMs need to be updated to have the newer boost.

      See http://kb.askmonty.org/en/installing-the-boost-library-needed-for-the-oqgraph-storage-engine

      When upgrading boost, update the above KB page too.


      OQGraph fails to compile with a new Boost. We're waiting for Anthony to fix it.

      Attachments

        Issue Links

          Activity

            dbart Daniel Bartholomew added a comment - I've documented what I did to upgrade the VMs here: https://kb.askmonty.org/en/installing-the-boost-library-needed-for-the-oqgraph-storage-engine
            arjen Arjen Lentz added a comment -

            The problem report is confusing: it self-contradicts, and notes other unlikely scenarios. Therefore it's not clear what needs to be done to fix the problem, if indeed there is a problem.

            a) why would the same OQGraph code in a different MariaDB branch suddenly require a different version of Boost? (MariaDB 5.5 needing Boost 1.45 - where is that requirement seen?)
            b) on the one hand it's stated that OQGraph does not build with a new Boost, but all the Boost versions listed are higher than the minimum requirement that OQGraph code has.
            c) Serg writes "OQGraph fails to build or crashes in tests in different VMs. In a couple of VMs it passes all tests." - it'd be handy to know what status it has in which environments, and what the build errors are, and test crash reports?

            Please will the people who detected the issues provide the info they saw, so someone can actually fix it?
            Come on guys - if you get a bug report of this nature, can you magically resolve it?
            Your help is appreciated. thanks

            arjen Arjen Lentz added a comment - The problem report is confusing: it self-contradicts, and notes other unlikely scenarios. Therefore it's not clear what needs to be done to fix the problem, if indeed there is a problem. a) why would the same OQGraph code in a different MariaDB branch suddenly require a different version of Boost? (MariaDB 5.5 needing Boost 1.45 - where is that requirement seen?) b) on the one hand it's stated that OQGraph does not build with a new Boost, but all the Boost versions listed are higher than the minimum requirement that OQGraph code has. c) Serg writes "OQGraph fails to build or crashes in tests in different VMs. In a couple of VMs it passes all tests." - it'd be handy to know what status it has in which environments, and what the build errors are, and test crash reports? Please will the people who detected the issues provide the info they saw, so someone can actually fix it? Come on guys - if you get a bug report of this nature, can you magically resolve it? Your help is appreciated. thanks

            Arjen, I've created new bug for this. Please see MDEV-336 for details

            serg Sergei Golubchik added a comment - Arjen, I've created new bug for this. Please see MDEV-336 for details

            oqgraph is now in debs (on distributions with a sufficiently new gcc, e.g not on hardy)

            serg Sergei Golubchik added a comment - oqgraph is now in debs (on distributions with a sufficiently new gcc, e.g not on hardy)

            oqgraph is now in debs in bintars, where possible

            serg Sergei Golubchik added a comment - oqgraph is now in debs in bintars, where possible

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              1 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.