[MDEV-13812] Is it possible to get rid of Advance Toolchain when building MariaDB for ppc? Created: 2017-09-15  Updated: 2018-12-18  Resolved: 2018-12-18

Status: Closed
Project: MariaDB Server
Component/s: Compiling
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Andrey Nevolin Assignee: Daniel Bartholomew
Resolution: Fixed Votes: 0
Labels: None

Sprint: 10.3.3-1

 Description   

Hi,

MariaDB dependency on Advance Toolchain for ppc is problematic (you can find some details in MDEV-13804 and MDEV-13811).

Dependency of Galera on Boost is also a problem for this architecture.

Is it possible to make MariaDB free of these dependencies?

This is just an inquiry. No pressure in any way. I'm trying to figure out a way of using this wonderful DB on ppc. But unfortunately currently I don't see a way which wouldn't be very painful and wouldn't break standard Linux support contracts.

 Comments   
Comment by Sergey Vojtovich [ 2017-10-20 ]

I already expressed my concerns re AT in MDEV-11386. In a nutshell I'm all for getting rid of it or at the very least having non-AT builds.

Comment by Sergei Golubchik [ 2017-10-31 ]

ok, let's get rid of advance toolchain

Comment by Sergey Vojtovich [ 2017-10-31 ]

dbart, your turn

Hopefully all we need to do is remove PATH setting on P8 builders.

Comment by Daniel Bartholomew [ 2018-01-18 ]

I've removed the PATH setting for the IBM P8 builders. So naturally they immediately started having build issues.

However, with that said, we're moving away from the IBM-provided builders and to kvm-based builders.

To that end, the kvm-rpm-centos73-ppc64 and kvm-rpm-centos73-ppc64le builders are now in place and taking over for p8-rhel7 and p8-rhel71 (respectively). These builders have actually been running for a while, but were in the 'experimental' category on buildbot because of some lingering AT dependencies with the 'shared' rpm that is used during building. I was able to get that fixed yesterday and so I've just now moved the builders out of 'experimental' and into 'main'.

I will next deactivate the p8-rhel7 and p8-rhel71 builders. After I'm done with that the only IBM P8 builders left will be p8-suse12 and p8-rhel6. So those two will have to be looked at to make sure they're able to build without AT, but we don't need to worry about the p8-rhel7 and p8-rhel71 builders.

Comment by Daniel Black [ 2018-01-19 ]

Now that you've migrated away from AT 659047b8207a1212adeaa80c23b22da929f22b1b (10.0 branch and up) can be reverted.

I thought docker for the builders was the goal? ( MDEV-12508 ) anyway either works.

To get debug symbol rpms (MDEV-4646), can you install a cmake-3.7.0+ version like MDEV-11258 and use this for the RPM production job. EPEL still only has cmake-3.6 I'm afraid.

Sorry I don't know if rhel6/suse12 have native compilers of sufficient version for p8 builds of mariadb and don't have any close by to test sorry.

Comment by Daniel Bartholomew [ 2018-12-18 ]

Going through and closing old issues of mine that should have been closed a long time ago.

This task is done. All of our current ppc64 and ppc64le builds are made without the advanced toolchain (and have been for some time).

Generated at Thu Feb 08 08:08:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.