Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1951

posix_memalign not being detected on Fedora 22

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major - P3
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: WT2.6.1
        • Labels:
          None
        • # Replies:
          1
        • Last comment by Customer:
          true

          Description

          After upgrading a test machine to Fedora 22, the posix_memalign function is no longer being found by configure. It looks like setting _GNU_SOURCE may no longer be sufficient for posix_memalign to be available.

            Issue Links

            links to

            Web Link https://github.com/wiredtiger/wiredtiger/pull/2002

              Activity

              • Comments
              Hide
              Permalink
              xgen-internal-githook Githook User added a comment -

              Author:

              {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'}

              Message: Add code from the autoconf archive to detect posix_memalign instead of relying on AC_CHECK_FUNCS.

              refs WT-1951
              Branch: develop
              https://github.com/wiredtiger/wiredtiger/commit/ecc674b8f5fc58c1df9a1c6b957491d73a27603d

              Show
              xgen-internal-githook Githook User added a comment - Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@mongodb.com'} Message: Add code from the autoconf archive to detect posix_memalign instead of relying on AC_CHECK_FUNCS. refs WT-1951 Branch: develop https://github.com/wiredtiger/wiredtiger/commit/ecc674b8f5fc58c1df9a1c6b957491d73a27603d

                People

                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Days since reply:
                    2 years, 2 weeks, 1 day ago
                    Date of 1st Reply: