severity 816980 normal
retitle 816980 julia: Please do not use more CPUs than available.
thanks
Sorry, I can't reproduce this consistently, but when the problem
happens, I see a segfault like this in dmesg:
[ 5377.752190] julia[21086]: segfault at 2ffe2 ip 7f033628b807 sp
7ffc819cbdb
Processing commands for cont...@bugs.debian.org:
> severity 816980 normal
Bug #816980 [src:julia] julia: FTBFS in testing
Severity set to 'normal' from 'serious'
> retitle 816980 julia: Please do not use more CPUs than available.
Bug #816980 [src:julia] julia: FTBFS in testing
Changed Bug title to
On Tue, Apr 26, 2016 at 05:05:07PM +0200, Graham Inggs wrote:
> I attach the complete build log for the 1 CPU and 1GB build.
> The others logs look very similar.
I found this difference. First file is mine, second file is yours:
@@ -983,8 +228,8 @@
checking for ranlib... ranlib
checking comman
Hi Santiago
I set up a Debian Testing amd64 VM in VirtualBox, initially with 2 CPUs
and 4GB which I later reduced.
I successfully built julia 0.4.5-3 with 2 CPUS and 4GB, 2 CPUS and 2GB,
1 CPU and 4GB, 1 CPU and 2GB and finally 1 CPU and 1GB.
I attach the complete build log for the 1 CPU an
Hi Santiago,
On Mon, Apr 25, 2016 at 09:24:51PM +0200, Santiago Vila wrote:
> Question: Why should this package be the only one which does not work
> with eatmydata? Are there good reasons for the build system to be
> incompatible with eatmydata? Could julia be made compatible with
> eatmydaya aga
retitle 816980 julia: FTBFS in testing
thanks
Ok, there seems to be some kind of incompatibility between julia and
eatmydata. My /etc/schroot/chroot.d/stretch file for sbuild was like
this:
[stretch]
type=directory
description=Debian stretch
directory=/chroot/stretch
groups=sbuild
root-groups=sbu
Processing commands for cont...@bugs.debian.org:
> retitle 816980 julia: FTBFS in testing
Bug #816980 [src:julia] julia: FTBFS in testing (signal (11): Segmentation
fault)
Changed Bug title to 'julia: FTBFS in testing' from 'julia: FTBFS in testing
(signal (11): Segmentation fault)'.
> thanks
St
On Mon, Apr 25, 2016 at 09:15:35AM -0700, Tony Kelman wrote:
> 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 removin
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 brok
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 wrote:
>
> severity 816980 serious
> thanks
>
> I rented a virtual machine with 16
Processing commands for cont...@bugs.debian.org:
> severity 816980 serious
Bug #816980 [src:julia] julia: FTBFS in testing (signal (11): Segmentation
fault)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
816980: http://
11 matches
Mail list logo
