From: "Alexander V. Tikhonov" <avtikhon@tarantool.org> To: Kirill Yukhin <kyukhin@tarantool.org>, Alexander Turenko <alexander.turenko@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH v1 1/6] build: static build needs more cleanup in sources Date: Fri, 26 Jun 2020 17:22:33 +0300 [thread overview] Message-ID: <e3486cbb49bae34023af06b7b685b03f7e908408.1593181262.git.avtikhon@tarantool.org> (raw) Building Tarantool sources on make command run may fail with: [ 10%] make[2]: *** [test/small] Error 1 [ 10%] make[1]: *** [test/CMakeFiles/symlink_small_tests.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... The root cause of the issue that Dockerfile.staticbuild uses local copy of sources: COPY . /tarantool Which may have broken links in tests, like: $ ls -al test ... luajit-tap -> /<wrong path>/third_party/luajit/test small -> /<wrong path>/src/lib/small/test/ ... To fix the issue this links should be removed from the docker local copy of sources before build, like: rm -rf test/small test/luajit-tap Closes #5025 --- Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-4874-out-of-source-build-full-ci Issue: https://github.com/tarantool/tarantool/issues/5025 Dockerfile.staticbuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dockerfile.staticbuild b/Dockerfile.staticbuild index 253f2d5e9..f67f46f5e 100644 --- a/Dockerfile.staticbuild +++ b/Dockerfile.staticbuild @@ -75,7 +75,7 @@ RUN set -x && \ RUN set -x && \ find . -name 'CMakeFiles' -type d -exec rm -rf {} + && \ find . -name 'CMakeCache.txt' -type f -delete && \ - rm -rf build + rm -rf build test/small test/luajit-tap RUN pip install -r /tarantool/test-run/requirements.txt -- 2.17.1
reply other threads:[~2020-06-26 14:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=e3486cbb49bae34023af06b7b685b03f7e908408.1593181262.git.avtikhon@tarantool.org \ --to=avtikhon@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=kyukhin@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1 1/6] build: static build needs more cleanup in sources' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox