From 59195e76fafbf2206f335379455ea61d204f3b21 Mon Sep 17 00:00:00 2001 From: sterni Date: Thu, 12 Aug 2021 16:01:11 +0200 Subject: docs(nix/buildLisp): mention drawback of non-parallel compilation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit To be fair this hardly matters since SBCL is quite fast, but compiling ironclad with ECL is quite the experience… Change-Id: Ib89cc50e5d557acec51fdb085bcbdfc99736221e Reviewed-on: https://cl.tvl.fyi/c/depot/+/3342 Tested-by: BuildkiteCI Reviewed-by: tazjin --- nix/buildLisp/README.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'nix/buildLisp') diff --git a/nix/buildLisp/README.md b/nix/buildLisp/README.md index 452f495deb..5ee560e056 100644 --- a/nix/buildLisp/README.md +++ b/nix/buildLisp/README.md @@ -18,6 +18,10 @@ restrictions should be highlighted: * Only SBCL is supported (though the plan is to add support for at least ABCL and Clozure CL, and maybe make it extensible) +* Parallel compilation is not possible: Since buildLisp doesn't encode + dependencies between components (i. e. source files) like ASDF, + it must compile source files in sequence to avoid errors due to + undefined symbols. ## Usage -- cgit 1.4.1