Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-13211

warning: initialization from incompatible pointer type mysql_send_query, mysql_real_query, mysql_stmt_prepare

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 10.2.6
    • 10.2.7
    • Compiling
    • Debian 8.8 x32 - Digitalocean

       # uname -a
      Linux framework 3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) i686 GNU/Linux

    Description

      [ 40%] Building C object libmariadb/libmariadb/CMakeFiles/mariadb_obj.dir/mariadb_lib.c.o
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:3968:3: warning: initialization from incompatible pointer type
      mysql_send_query,
      ^
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:3968:3: warning: (near initialization for ‘MARIADB_API.mysql_send_query’)
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:3970:3: warning: initialization from incompatible pointer type
      mysql_real_query,
      ^
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:3970:3: warning: (near initialization for ‘MARIADB_API.mysql_real_query’)
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:4021:3: warning: initialization from incompatible pointer type
      mysql_stmt_prepare,
      ^
      /var/tmp/mariadb_build/mariadb_src/libmariadb/libmariadb/mariadb_lib.c:4021:3: warning: (near initialization for ‘MARIADB_API.mysql_stmt_prepare’)

      Attachments

        Activity

          People

            georg Georg Richter
            dertin Guillermo Céspedes Tabárez
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.