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

Add testing coverage for static wt build

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.3.3, 4.2.4
    • Component/s: None
    • Labels:
      None

      Description

      We used to have a component of the wiredtiger-test-check-long job that compiled a static wt utility, to make sure it worked OK.

      That job was tied to tinderbox, and I wanted to be able to run the job on other machines, so I stripped it from that job. We should create a different job that is "wiredtiger-static-build", which could be tied to tinderbox (or we could make sure the required libraries are on all machines).

      The build steps are:

      cd build_posix
      cleanup() {
      	status=$?
      	cd ../
      	rm -f `ls -t jenkins*.tgz | sed '1,5d'`
      	tar czf $BUILD_TAG.tgz build_posix
      }
      ../configure --disable-shared --with-builtins=snappy,zlib
      make -j8
      rm -f wt
      make CC='eval "g++ -static"' || cleanup
      ./wt -V
      if [ $? -ne 0 ]; then
      	echo "Error, WT Utility was not generated or is not functioning"
          cleanup
      fi
      ldd wt || FAIL=1
      if [ $FAIL -ne 1 ]; then
      	echo "Error, WT util not is not statically linked"
          cleanup
          exit 1
      fi
      

        Attachments

          Activity

            People

            Assignee:
            ravi.giri Ravi Giri
            Reporter:
            alexander.gorrod Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: