Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-543

hash_insert, hash_delete and hash_free conflict with GnuTLS 3.6.14+

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.1, 3.2(EOL)
    • 3.2.0, 3.1.13
    • Other
    • None

    Description

      GnuTLS (somewhere after 3.6.8, but no later than 3.6.14) implemented functions hash_insert/hash_delete/hash_free. Now libmariadb cannot link statically with gnutls because of

      /usr/local/bin/ld: /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../libgnutls.a(hash.o): in function `hash_free':
      hash.c:(.text+0xb78): multiple definition of `hash_free'; CMakeFiles/mariadb_obj.dir/ma_hash.c.o:/home/buildbot/buildbot/build/libmariadb/libmariadb/ma_hash.c:73: first defined here
      /usr/local/bin/ld: /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../libgnutls.a(hash.o): in function `hash_insert':
      hash.c:(.text+0x15a3): multiple definition of `hash_insert'; CMakeFiles/mariadb_obj.dir/ma_hash.c.o:/home/buildbot/buildbot/build/libmariadb/libmariadb/ma_hash.c:291: first defined here
      /usr/local/bin/ld: /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.8.5/../../../libgnutls.a(hash.o): in function `hash_delete':
      hash.c:(.text+0x189b): multiple definition of `hash_delete'; CMakeFiles/mariadb_obj.dir/ma_hash.c.o:/home/buildbot/buildbot/build/libmariadb/libmariadb/ma_hash.c:425: first defined here
      

      Suggestion: rename them in C/C if they aren't part of the exported client API

      Attachments

        Activity

          People

            georg Georg Richter
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.