[MDEV-16160] Upgrade p8-suse12 to gcc 4.8.5 Created: 2018-05-14  Updated: 2018-05-31  Resolved: 2018-05-31

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

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Daniel Bartholomew
Resolution: Fixed Votes: 0
Labels: buildbot, portability

Issue Links:
Relates
relates to MDEV-15437 power crc32 c implementation Closed

 Description   

As noted in the pull request of MDEV-15437, we should upgrade the GCC on our POWER8 SuSE 12 build host, so that it can compile the code. The old GCC 4.8.3 cannot handle it, but the GCC 4.8.5 from July 2015 should work.



 Comments   
Comment by Daniel Bartholomew [ 2018-05-14 ]

gcc has been updated to 4.8.5 on the p8-suse12-rpm builder

u0013565@sys-93188:~> gcc --version
gcc (SUSE Linux) 4.8.5

Let me know if there are other tasks to do or if this can be closed.

Thanks.

Comment by Daniel Black [ 2018-05-14 ]

I don't think so but lets wait until a 10.3 branch builds with 4.8.5 first. Thanks dbart

Comment by Daniel Black [ 2018-05-15 ]

Passes compile ok : http://buildbot.askmonty.org/buildbot/builders/p8-suse12-rpm/builds/4787 - mtr not finished.

Looked though configure stage to see what's missing (Judy - doesn't exist as SUSE package), libnuma (was getting removed in 10.3 i thought), few compression things in connector C (which don't seem used).

So seems ok AFAIK.

Thanks again.

Comment by Daniel Black [ 2018-05-15 ]

maybe cmake-3.7+ so there is Debug RPM packages like MDEV-4646. Minor only as the repo isn't advertised.

ccache, and -DCMAKE_C_COMPILER_LAUNCHER=ccache -DCMAKE_CXX_COMPILER_LAUNCHER=ccache (cmake-3.5+?) or add ccache to -DCMAKE_C_COMPILER="ccache gcc" -DCMAKE_CXX_COMPILER="ccache g++" (might need full paths) for older CMake versions. Not sure how much success you've had with ccache, setting environment CCACHE_DIR per major branch probably will help.

Comment by Marko Mäkelä [ 2018-05-15 ]

dbart, is it intentional that there are no tests run on the platform?

Comment by Daniel Bartholomew [ 2018-05-15 ]

marko I think tests were supposed to be added, but they never were. I remember the builder being set up in a hurry, so tests were probably skipped initially in favor of getting the basic builder in place. I'm sure tests were meant to be added eventually, but they never were.

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