[MDEV-15138] ubuntu arm64 fails to build packages with mroonga disabled Created: 2018-01-31 Updated: 2018-03-14 Resolved: 2018-03-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Mroonga |
| Affects Version/s: | 10.2.12 |
| Fix Version/s: | 10.2.14, 10.3.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Thompson (Inactive) | Assignee: | Daniel Bartholomew |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Epic Link: | arm64 optimization | ||||||||
| Description |
|
buildbot fails to build 10.2.12 and 10.3 on arm64 ubuntu due to a change that was introduced in 10.2.12. Since mroonga hits some compiler errors that we don't have workarounds for this was disabled as an engine in the arm64 build, however now the ubuntu build fails because the deb packaging code assumes it should be there. AFAIK it's our favorite feature of debian packaging, where components are listed explicitly. You've disabled compilation just fine, it doesn't compile anymore, but debian still wants to package it, hence the problem. A mechanism to silently drop a package if the plugin wasn't built backfired at us just recently with the TokuDB loss, so I don't expect that Sergei is eager to add it [back]. For some plugins which build conditionally we have the conditions in different places – debian/autobake-deb.sh, debian/rules, or whatever, but apparently we don't have one (or the right one) for Mroonga yet. If we want to continue not building it, it needs to be added. |
| Comments |
| Comment by David Thompson (Inactive) [ 2018-01-31 ] |
|
to repro: also to speed things up, it's smart to edit autobake-deb.sh to add -j46 (or 48 if has full core count): |
| Comment by David Thompson (Inactive) [ 2018-01-31 ] |
|
http://buildbot.askmonty.org/buildbot/builders/arm64-xenial-deb/builds/228/steps/compile/logs/stdio is an example from 10.3 |
| Comment by Sergey Vojtovich [ 2018-02-16 ] |
|
dbart, there's a workaround for mroonga in 10.1 now (not merged up as of this writing). Please enable mroonga. And sorry for this confusion, I thought we had code to skip mroonga if it didn't build. |
| Comment by Daniel Bartholomew [ 2018-03-14 ] |
|
Thanks svoj, I've renabled mroonga, and the builder is now successfully building packages |