Probably because the Debian build isn't using the stable, tested, recommended and supported version of LLVM for that branch of Julia. LLVM makes significant breaking changes to all of their API's between minor versions, so removing old versions from Debian means downstream users of LLVM end up broken or with serious performance and memory regressions. On Apr 25, 2016 9:10 AM, "Viral Shah" <vi...@juliacomputing.com> wrote:
> I routinely build Julia on my 8GB Macbook Pro, and it comfortably builds > with a bunch of other stuff running. > > Tony, Elliot - either of you have any ideas? > > -viral > > > > > On 25-Apr-2016, at 8:17 PM, Santiago Vila <sanv...@unex.es> wrote: > > > > severity 816980 serious > > thanks > > > > I rented a virtual machine with 16 GB RAM and 16 GB swap. > > It failed again. The build log is attached. > > > > While it was working, "top" showed this: > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND > > 8453 sanvila 20 0 9209844 504260 66120 R 99.7 6.2 2:42.93 julia > > 8677 sanvila 20 0 9002012 272516 62216 R 100.3 3.3 0:54.40 julia > > 7954 sanvila 20 0 9105584 163172 56504 S 0.0 2.0 0:09.03 julia > > > > Do I need 27 GB of RAM to build this now? > > > > If not: How much swap do I need, why does julia overcommit so much, > > and why this didn't happen in version 0.3.11 or 0.3.12? > > > > > Thanks.<julia_0.4.5-3_amd64-20160425-0957.build.gz>_______________________________________________ > > Pkg-julia-devel mailing list > > pkg-julia-de...@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel > >