Details

    • 10.2.0-3

    Description

      As reported on IRC: using gcc-5.3 and binutils-2.25.1 on gentoo, compilation fails with errors from ar like

      /var/tmp/portage/dev-db/mariadb-10.1.9-r1/work/mysql-abi_x86_32.x86/libmysql/libmysql_exports_file.cc:38:15: error: function 'mysql_get_client_version' redeclared as variable

      Attachments

        Activity

          grknight Brian Evans added a comment -

          My Gentoo install builds fine with MariaDB 10.1.9, binutils 2.25.1 and gcc 5.3

          grknight Brian Evans added a comment - My Gentoo install builds fine with MariaDB 10.1.9, binutils 2.25.1 and gcc 5.3

          We have not seen this compile error either. But someone reported the mentioned build error on IRC.

          wlad Vladislav Vaintroub added a comment - We have not seen this compile error either. But someone reported the mentioned build error on IRC.

          Can reproduce the error with -flto. This is likely how the user has compiled, it is a linker that reports error

          MySQL's bug is here https://bugs.mysql.com/bug.php?id=67790

          wlad Vladislav Vaintroub added a comment - Can reproduce the error with -flto. This is likely how the user has compiled, it is a linker that reports error MySQL's bug is here https://bugs.mysql.com/bug.php?id=67790
          wlad Vladislav Vaintroub added a comment - - edited

          Fixed by using -fno-lto for the generated file, if -flto is set in compile flags

          wlad Vladislav Vaintroub added a comment - - edited Fixed by using -fno-lto for the generated file, if -flto is set in compile flags

          People

            wlad Vladislav Vaintroub
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.