[MDEV-19481] mariadb-10.3.15-linux-systemd-x86_64/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' and 'GLIBCXX_3.4.21' not found Created: 2019-05-15 Updated: 2020-08-25 Resolved: 2019-08-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Packaging |
| Affects Version/s: | 10.3.15, 10.4 |
| Fix Version/s: | 10.2.26, 10.1.41, 10.3.17, 10.4.7 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Christian Weiss | Assignee: | Daniel Bartholomew |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Red Hat Enterprise Linux Server release 7.6 (Maipo) |
||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
I wanted to update from 10.3.14 to 10.3.15 community version (mariadb-10.3.15-linux-systemd-x86_64.tar.gz), but because of version mismatch mysqld won't run:
Last "yum update" of Red Hat was March 2019. |
| Comments |
| Comment by Sergei Golubchik [ 2019-07-07 ] |
|
dbart, please change your release scripts (or whatever needs to be changed) to use trusty instead of xenial for systemd bintars. |
| Comment by Daniel Bartholomew [ 2019-07-23 ] |
|
I've updated my release scripts. The trusty bintar builds will be used going forward. |
| Comment by Daniel Bartholomew [ 2019-07-31 ] |
|
I am using the trusty-built bintars now for the latest 10.3.17 that was just released. cweiss Can you verify that the version mismatch is resolved? |
| Comment by Christian Weiss [ 2019-08-01 ] |
|
Hereby I verified that the version mismatch is resolved. |