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

OQGraph should be disabled for POWER8 Ubuntu package builds

Details

    • 10.1.9-2, 10.1.9-3

    Description

      On POWER8, the libjudydebian1 package is empty except for the copyright and changelog files:

      u0016471@sys-74005:~$ dpkg -L libjudydebian1
      /.
      /usr
      /usr/lib
      /usr/share
      /usr/share/doc
      /usr/share/doc/libjudydebian1
      /usr/share/doc/libjudydebian1/copyright
      /usr/share/doc/libjudydebian1/changelog.Debian.gz

      This leads to issues when compiling:

      • If the libjudydebian1 and libjudy-dev packages are not installed, building MariaDB fails with the following failure:

        dpkg-checkbuilddeps: Unmet build dependencies: libjudy-dev
        dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting

      Log: http://buildbot.askmonty.org/buildbot/builders/p8-trusty-deb/builds/616/steps/compile/logs/stdio

      • If the two packages are installed, building MariaDB fails with the following failure:

      make[3]: *** No rule to make target `/usr/lib/libJudy.so', needed by `storage/oqgraph/ha_oqgraph.so'.  Stop.

      Log: http://buildbot.askmonty.org/buildbot/builders/p8-trusty-deb/builds/615/steps/compile/logs/stdio

      We should disable building OQGraph on POWER8 and remove the dependency on the libjudy-dev package, at least until the libjudydebian1 package gets fixed upstream.

      Attachments

        Issue Links

          Activity

            I'd rather build and install libjudydebian1 on the power8 builder

            serg Sergei Golubchik added a comment - I'd rather build and install libjudydebian1 on the power8 builder

            serg: So you're saying we build the library from source on that box and then include it in our packages?

            dbart Daniel Bartholomew added a comment - serg : So you're saying we build the library from source on that box and then include it in our packages?

            I think taking on responsibility for building and maintaining libjudy-dev on our own makes no sense. I vote that we skip OQGraph on POWER8 and remove the libjudy-dev dependency (MDEV-9111).

            kolbe Kolbe Kegel (Inactive) added a comment - I think taking on responsibility for building and maintaining libjudy-dev on our own makes no sense. I vote that we skip OQGraph on POWER8 and remove the libjudy-dev dependency ( MDEV-9111 ).
            danblack Daniel Black added a comment - - edited

            (untested) you could potentially install a libjudy-dev package from Debian to build leave end users having to do the same.

            Hopefully ubuntu distro maintainers can make it happen.

            danblack Daniel Black added a comment - - edited (untested) you could potentially install a libjudy-dev package from Debian to build leave end users having to do the same. Hopefully ubuntu distro maintainers can make it happen.

            danblack, it worked, thanks for your idea.

            First successful build:
            http://buildbot.askmonty.org/buildbot/builders/p8-trusty-deb/builds/648

            Build fixed by installing libjudy-dev_1.0.5-4_ppc64el.deb, libjudydebian1_1.0.5-4_ppc64el.deb of Debian Jessie. However oqgraph package won't be functional without installing these packages, which should be acceptable.

            svoj Sergey Vojtovich added a comment - danblack , it worked, thanks for your idea. First successful build: http://buildbot.askmonty.org/buildbot/builders/p8-trusty-deb/builds/648 Build fixed by installing libjudy-dev_1.0.5-4_ppc64el.deb, libjudydebian1_1.0.5-4_ppc64el.deb of Debian Jessie. However oqgraph package won't be functional without installing these packages, which should be acceptable.

            People

              svoj Sergey Vojtovich
              dbart Daniel Bartholomew
              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.