23 Commits (feda2c8e3180cb983c35976d4440cea23a155b7f)

Author	SHA1	Message	Date
Yerzhan Mazhkenov	94c7dd9ac8	doc: Fix typos from codespell lint	4 years ago
Carl Dong	d55a1056ee	guix: Add troubleshooting documentation entries	4 years ago
Carl Dong	d5a71e9785	guix: Use --cores instead of --max-jobs ... In Guix, there are two flags for controlling parallelism: Note: When I say "derivation," think "package" --cores=n - controls the number of CPU cores to build each derivation. This is the value passed to `make`'s `--jobs=` flag. - defaults to 0: as many cores as is available --max-jobs=n - controls how many derivations can be built in parallel - defaults to 1 Therefore, if set --max-jobs=$MAX_JOBS and don't set --cores, Guix could theoretically spin up $MAX_JOBS * $(nproc) number of threads, and that's no good. So we could either default to --cores=1, --max-jobs=$MAX_JOBS - Pro: --cores=1 means that `make` will be invoked with `-j1`, avoiding problems with package whose build systems and test suites break when running multi-threaded. - Con: There will be times when only 1 or 2 derivations can be built at a time, because the rest of the dependency graph all depend on those 1 or 2 derivations. During these times, the machine will be severely under-utilized. or --cores=$MAX_JOBS, --max-jobs=1 - Pro: We don't encounter prolonged periods of severe under-utilization mentioned above. - Con: Many packages' build systems and test suites break when running multi-threaded. or --cores=1, --max-jobs=1 and let the user override with $ADDITIONAL_GUIX_COMMON_FLAGS	4 years ago
Hennadii Stepanov	a0a7a4337d	guix, doc: Update default HOSTS value	4 years ago
Carl Dong	13a9fd11a5	guix: Passthrough SDK_PATH into container	4 years ago
Carl Dong	95990b9f32	guix: Update conservative space requirements	4 years ago
Carl Dong	901f54321b	guix: Passthrough BASE_CACHE into container ... This allows depends-built packages to be cached.	4 years ago
MarcoFalke	fa051c2386	doc: Guix is shipped in Debian and Ubuntu	4 years ago
Carl Dong	771c4b98a8	guix: README: Add darwin HOSTS entry	4 years ago
Carl Dong	34f0fda2d3	guix: Small updates to README wording	4 years ago
Carl Dong	402e3a5b1e	guix: Update HOSTS README entry for new architectures	4 years ago
Carl Dong	cfa7ceb21b	guix: Remove README development environment section	4 years ago
Carl Dong	93b6a8544a	guix: Add ADDITIONAL_GUIX_{COMMON,TIMEMACHINE}_FLAGS options	4 years ago
Carl Dong	0f31e24703	guix: Add SUBSTITUTE_URLS option	4 years ago
Carl Dong	f852761aec	guix: Add clarifying documentation for V env var	5 years ago
Carl Dong	1f2c39a30e	guix: Remove logical cores requirement ... Thanks MarcoFalke for pushing this to its limits and testing :-)	5 years ago
Carl Dong	c4cce00eac	guix: Remove dead links from README.	5 years ago
MarcoFalke	fae9084ac5	build: Skip i686 build by default in guix and gitian	5 years ago
Carl Dong	88c83636d5	guix: Update documentation for time-machine ... Wait a minute, doc. Are you telling me you built a time machine... Out of a functional package manager?	5 years ago
Carl Dong	751549b52a	contrib: guix: Additional clarifications re: substitutes	5 years ago
Carl Dong	cd3e947f50	contrib: guix: Various improvements. ... - Clearer and more accurate prose - Pin `guix pull' to commit rather than branch - Just use `use-module' instead of `define-module' - Use `bash-minimal' instead of `bash' - Remove unneeded `tcsh' from manifest - Explicitly use `python-3.7' - Add comments about how {native,cross}-toolchains are produced and why	5 years ago
Carl Dong	8dff3e48a9	contrib: guix: Clarify SOURCE_DATE_EPOCH.	5 years ago
Carl Dong	3e80ec3ea9	contrib: Add deterministic Guix builds.	5 years ago