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

Centos 6 32 bits: Release build error: my_context.c:454: Error: CFI instruction used without previous .cfi_startproc

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.1
    • 2.3.6
    • None
    • None
    • Centos 6.6 32 bits

    Description

      cmake -DCMAKE_BUILD_TYPE=Release on Centos 6 32 bits:

      [ 44%] Building C object libmariadb/CMakeFiles/mariadb_obj.dir/my_context.c.o
      		 
      /home/3rdParty-build/src/mariadb-connector-c-2.1.0-src/libmariadb/my_context.c: Assembler messages:
      		 
      /home/3rdParty-build/src/mariadb-connector-c-2.1.0-src/libmariadb/my_context.c:454: Error: CFI instruction used without previous .cfi_startproc
      		 
      make[2]: *** [libmariadb/CMakeFiles/mariadb_obj.dir/my_context.c.o] Error 1

      With debug symbols it works:
      cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo

      (It also works on 64 bits).

      This was also encountered by https://github.com/mscdex/node-mariasql/issues/18

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17127 compiling mariadb-10.3.9 report error

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9802 [PATCH] Build fails on SmartOS and gcc 4.9.3

          • Major - Major loss of function.
          • Open

          Activity

            People

              georg Georg Richter
              trsystran Thomas Riccardi
              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.