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

Undefined symbol "uncompress" in s3_get_object()

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.5
    • 10.5.5
    • Storage Engine - Aria
    • None
    • Mac OS X (mac-1012-bintar)

    Description

      MariaDB 10.5 fails to build on Mac OS X due to the following:

      10.5 c69520c9dfa6e4a26258842a1d3512c2b5d43d56

      		 
      [ 91%] Linking CXX shared module ha_s3.so
      		 
      Undefined symbols for architecture x86_64:
      		 
        "_uncompress", referenced from:
      		 
            _s3_get_object in s3_func.c.o
      		 
      ld: symbol(s) not found for architecture x86_64
      		 
      clang: error: linker command failed with exit code 1 (use -v to see invocation)
      		 
      make[2]: *** [storage/maria/ha_s3.so] Error 1

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25092 S3 doesn't get disabled properly if zlib-devel is not installed on the system

          • Major - Major loss of function.
          • Open
          is caused by

          Task - A task that needs to be done. MDEV-17841 S3 Storage engine

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23377 libmarias3 doesn't compile in OpenBSD

          • Major - Major loss of function.
          • Closed

          Activity

            People

              danblack Daniel Black
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.