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

No way to use prebuilt packages on SLES12sp2-ppc64le

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.2.8
    • N/A
    • Configuration
    • None

    Description

      MariaDB prebuilt packages cannot be used on SLES12sp2-ppc64le because it's impossible to satisfy some dependencies by combining prebuit packages.

      Consider the following dependencies:
      1) mysqld -> libsystemd.so -> glibc
      2) garbd -> libboost_program_options.so.1.55

      Next, MariaDB 10.2 packages were built using Advance Toolchain 8.0.

      Advance Toolchain doesn't substitute "libsystemd" library. So, a SLES version will be used. This version depends on SLES version of "glibc" which is 2.22. But Advance Toolchain 8.0 comes with version 2.20. Exactly this version will be loaded by Advance Toolchain loader. Loading "libsystemd" will fail after that, because a more recent version of "glibc" is required by this library.

      Ok, it's easy to fix that. One can install AT 9.0 and also a compatibility package for AT 8.0.

      AT 9.0 has "glibc 2.22" inside. Hence, "mysqld" dependency is satisfied.

      But "garbd" dependency is broken after that. Because AT 9.0 contains a more recent version of Boost. And compatibility mode doesn't provide access to AT 8.0 version of Boost.

      So,
      1) mysqld requires AT 9.0 (if executed on SLES12sp2)
      2) garbd requires exactly AT 8.0 (and AT 9.0-8.0 compatibility package cannot fix that)

      Attachments

        Activity

          People

            dbart Daniel Bartholomew
            Andrey Nevolin Andrey Nevolin
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.