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

Avoid collisions between WiredTiger Python wrapper naming and WiredTiger functions.

    • Type: Icon: Task Task
    • Resolution: Done
    • WT2.5.1
    • Affects Version/s: None
    • Component/s: None

      @ddanderson, an issue for the build problem where internal WiredTiger names like __wt_cursor_equals collide with names generated by the Python SWIG wrapper.

      wiredtiger_wrap.c:3442:16: error: conflicting types for ‘__wt_cursor_equals’
       SWIGINTERN int __wt_cursor_equals(struct __wt_cursor *self,WT_CURSOR *other){
                      ^
      In file included from /home/sue/wt.1571/build_posix/../src/include/wt_internal.h:318:0,
                       from wiredtiger_wrap.c:3010:
      /home/sue/wt.1571/build_posix/../src/include/extern.h:283:12: note: previous declaration
      of ‘__wt_cursor_equals’ was here
       extern int __wt_cursor_equals(WT_CURSOR *cursor, WT_CURSOR *other, int *equalp);
                  ^
      error: command 'gcc' failed with exit status 1
      

      Would you please take a look and see if there's a fix to keep this from happening again?

      If you want, feel free to revert 010059e when this is fixed.

            Assignee:
            donald.anderson@mongodb.com Donald Anderson
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: