Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38389

ccache: error: execv of @/tmp/tmpCwyvtv.lnk failed: No such file or directory

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.4
    • Component/s: Build
    • None
    • ALL
    • Hide
      • Try to build version 4.0.4 with the command { {buildscripts/scons.py AR="aarch64-linux-gnu-ar" CC="ccache aarch64-linux-gnu-gcc" CXX="ccache aarch64-linux-gnu-g++" HOST_ARCH="x86_64" TARGET_ARCH="aarch64" CCFLAGS="-march=armv8-a+crc" --disable-warnings-as-errors -j 6 mongod}

        }

      Show
      Try to build version 4.0.4 with the command { {buildscripts/scons.py AR="aarch64-linux-gnu-ar" CC="ccache aarch64-linux-gnu-gcc" CXX="ccache aarch64-linux-gnu-g++" HOST_ARCH="x86_64" TARGET_ARCH="aarch64" CCFLAGS="-march=armv8-a+crc" --disable-warnings-as-errors -j 6 mongod} }
    • Dev Tools 2018-12-17

      When trying to crosscompile MongoDB 4.0.4 for arm64/aarch64, the build fails with this rather strange error message:

      [2018-12-04 15:48:56 (01:41:57.323047)] ccache @/tmp/tmpCwyvtv.lnk
      [2018-12-04 15:48:56 (01:41:57.544064)] ccache: error: execv of @/tmp/tmpCwyvtv.lnk failed: No such file or directory
      

      The command line used for the build was buildscripts/scons.py AR="aarch64-linux-gnu-ar" CC="ccache aarch64-linux-gnu-gcc" CXX="ccache aarch64-linux-gnu-g++" HOST_ARCH="x86_64" TARGET_ARCH="aarch64" CCFLAGS="-march=armv8-a+crc" --disable-warnings-as-errors -j 6 mongod

      The complete build log is attached as a file.
      Note that the timestamping is happening through my build system. When running from a normal command line it's not there.

        1. build.log
          2.39 MB

            Assignee:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Reporter:
            ConnectingMedia Connecting Media
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: