I'm having the same issue on a fresh clone
My HEAD is at:
3c7136e 2015-03-02 (HEAD, origin/master, origin/HEAD, master) Docs:
cross-reference Pkg in git primer section [Jiahao Chen]
I've put my log here:
https://gist.githubusercontent.com/JonathanAnderson/7fa10f187c564c864817/raw/julia_build_failure
On Friday, February 27, 2015 at 12:31:19 PM UTC-6, [email protected]
wrote:
>
> Ok. I'll get to it ASAP. I also tried a completely fresh clone, and I get
> the same error.
>
> On Friday, February 27, 2015 at 3:59:52 PM UTC+1, Ivar Nesje wrote:
>>
>> Thanks for reporting
>>
>> The error seems to be coming from /src/gc.c#L482
>> <https://github.com/JuliaLang/julia/blob/32aee08d0b833233cd22b7b1de01ae769395b3b8/src/gc.c#L482>,
>>
>> which was added in #8699 <https://github.com/JuliaLang/julia/pull/8699>
>> which
>> was merged 24 Ja
>> <https://github.com/JuliaLang/julia/pull/8699#event-224146648>n
>> <https://github.com/JuliaLang/julia/pull/8699#event-224146648> (~30 days
>> ago)
>>
>> As nobody else has reported this, someone will probably need more
>> information about your system in order to debug this properly, as it likely
>> is system dependent. Can you try to download any of the pre-buildt binaries
>> to see if they work?
>>
>> Ivar
>>
>>
>>
>> fredag 27. februar 2015 14.18.55 UTC+1 skrev [email protected]
>> følgende:
>>>
>>> Anyone know something about this ?
>>>
>>> I did not build the latest Julia (master branch) since about 30 days.
>>> Now, when I do 'git pull' and 'make' I am getting various error messages:
>>>
>>> could not allocate pools
>>> Aborted
>>> Makefile:165: recipe for target
>>> '/home/jlapeyre/software_source/julia/usr/lib/julia/sys0.o' failed
>>>
>>> This was a few days ago, so I 'pulled' every once in a while, hoping the
>>> problem would go away.
>>> I tried make clean, make cleanall, make distcleanall. Then dependencies
>>> also fail to build
>>> I removed even the packages with make -C deps distcleanall.
>>>
>>> I have not changed my tool chain since the last successful build. I
>>> can't recall, but there is a
>>> chance (but, I think not) that I moved the entire repository from one
>>> place to another.
>>>
>>> Since I don't see any noise about this, something tells me its not a
>>> common problem.
>>>
>>> --John
>>>
>>
