[CONCPP-77] connector c++ is not buildable with rhel7, sles12 Created: 2021-04-14 Updated: 2021-05-10 Resolved: 2021-05-10 |
|
| Status: | Closed |
| Project: | MariaDB Connector/C++ |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Timofey Turenko | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
sles12, rhel7 |
||
| Description |
|
Connector c++ requires GCC 4.9, but sles12 and rhel7 have 4.8. the error message is confusing - "GCC versin >4.8 is required" - build error in rhel7 happens, but does not clarify the situation (rhel7 has gcc 4.8.5) changing https://github.com/mariadb-corporation/mariadb-connector-cpp/blob/master/CMakeLists.txt#L29 4.9 -> 4.8 fixes the problem also the condition:
does not work if compiler is not gnucc and does not check its version. |
| Comments |
| Comment by Timofey Turenko [ 2021-04-15 ] |
|
first build of yum repos for cpp https://mdbe-ci-repo.mariadb.net/ConnectorCpp/master-packages-apt14-03/yum/ all packages for C https://mdbe-ci-repo.mariadb.net/ConnectorC/3.1-packages-apr15/ |
| Comment by Timofey Turenko [ 2021-04-15 ] |
|
"GCC versin >4.8 is required" - letter 'o' is missing in versin |
| Comment by Lawrin Novitsky [ 2021-04-15 ] |
|
This(gcc version check) is obviously added on purpose. Connector can be built with 4.8, but is not usable. On sles12 it's possible to natively install gcc5(via suse toolchain module) and use it for build. On centos7 you can ask dbart about the tricks he does to build it. Not sure if this tricks are suitable for you, though. |
| Comment by Timofey Turenko [ 2021-04-18 ] |
|
Please at least fix the error message: it is misleading - "GCC versin >4.8 is required" - RHEL7 has 4.8.5 which is >4.8, but for build we need >= 4.9 I added installation of newer gcc to slse12 and rhel7, but there is not test yet for resulting packages. |
| Comment by Lawrin Novitsky [ 2021-05-10 ] |
|
I am closing this issue, as there is nothing more to do here since error message has been corrected, and it is unlikely an appropriate place to discuss packaging on this platforms. |