Leo Prikler <[email protected]> writes: > There could potentially be another workaround by synchronizing inside > guild, i.e. claiming a lock before reading and evaling any given source > file. This would have the advantage of applying to all guile packages, > not just the ones that use guile-build-system, and it would also allow > non-Guile stuff, e.g. C extensions to be built in parallel. WDYT?
I don't think this would solve the problem, because it wouldn't ensure that the Guile modules are compiled in a deterministic order, and therefore the issue I raised in <https://bugs.gnu.org/20272#8> would lead to nondeterministic results. Mark
