I'm now down to 2,2G ./julia-0.4 1,7G ./julia-0.5
which is good enough to stop the low disk space warnings :D I'll be eagerly awaiting that PR, Jameson! ;) Thanks, all! // T On Wednesday, August 10, 2016 at 6:19:23 PM UTC+2, Jameson wrote: > > Yes, you can delete anything old (the same goes for usr-staging and > deps/srccache). I've also been slowly developing a PR that will allow the > build system to automatically erase the build directories after its > finished with them, but it's not ready yet. But someday... > > > > On Wednesday, August 10, 2016 at 5:33:50 AM UTC-4, Tomas Lycken wrote: >> >> Thanks for the replies. >> >> Is it safe to assume that anything in deps/build that exists in multiple >> versions, is only needed in the latest of those? For instance, I have >> >> ``` >> 159M deps/build/llvm-3.3 >> 318M deps/build/llvm-3.7.1 >> 881M deps/build/openblas-12ab1804b6ebcd38b26960d65d254314d8bc33d6 >> 943M deps/build/openblas >> ``` >> >> where it seems I could shave off a GB or so by deleting `llvm-3.3` and >> `openblas-<hash>`. `deps/srccache` is another 650 MB, can that also be >> deleted? >> >> My main reason for building from source rather than using the binaries is >> that now and then I stumble on something I want to investigate and/or >> improve in base, and the threshold for actually filing a PR is much lower >> if I already have the code I'm running locally. Once 0.5 is out for real >> I'll probably drop the source tree for 0.4, so "temporarily" freeing up a >> couple of gigs by deleting build intermediates is good enough for now. >> >> // T >> >> On Wednesday, August 10, 2016 at 10:49:38 AM UTC+2, Andreas Lobinger >> wrote: >>> >>> Hello colleague, >>> >>> On Wednesday, August 10, 2016 at 10:11:46 AM UTC+2, Tomas Lycken wrote: >>>> >>>> Both instances of Julia are runnable, so I don’t think I deleted >>>> something I shouldn’t have in either folder. >>>> >>>> What has changed to make Julia 0.5 so big? Are there any build >>>> artifacts I can/should prune to reduce this footprint? >>>> >>> my guess it's some cumulative build artefacts: >>> >>> lobi@orange4:~/julia05/deps$ du -sh * >>> 8,0K arpack.mk >>> 12K blas.mk >>> 4,8G build >>> 508K checksums >>> 4,0K dsfmt.mk >>> 8,0K fftw.mk >>> 4,0K gfortblas.alias >>> 8,0K gfortblas.c >>> 4,0K gmp.mk >>> 4,0K libdSFMT.def >>> 4,0K libgit2.mk >>> 4,0K libgit2.version >>> 4,0K libssh2.mk >>> 4,0K libssh2.version >>> 4,0K libuv.mk >>> 4,0K libuv.version >>> 20K llvm.mk >>> 4,0K llvm-ver.make >>> 8,0K Makefile >>> 4,0K mbedtls.mk >>> 4,0K mpfr.mk >>> 4,0K NATIVE.cmake >>> 4,0K objconv.mk >>> 4,0K openblas.version >>> 4,0K openlibm.mk >>> 4,0K openlibm.version >>> 4,0K openspecfun.mk >>> 4,0K openspecfun.version >>> 4,0K patchelf.mk >>> 328K patches >>> 4,0K pcre.mk >>> 2,0G srccache >>> 8,0K suitesparse.mk >>> 4,0K SuiteSparse_wrapper.c >>> 20K tools >>> 4,0K unwind.mk >>> 4,0K utf8proc.mk >>> 4,0K utf8proc.version >>> 384K valgrind >>> 4,0K Versions.make >>> 4,0K virtualenv.mk >>> >>>
