Bug#849815: closed by Peter Colberg <pe...@colberg.org> (Bug#849815: fixed in julia 0.4.7-3)

[Tony Kelman]

Thank you Peter! That looks like it should do the trick.

Bug#849815: julia: Please set TAGGED_RELEASE_BANNER to identify Debian package builds

[Tony Kelman]

Package: julia
Version: 0.4.7-2
Severity: wishlist

Dear Maintainer,

In order to more clearly identify when an issue gets reported upstream
by someone who may be using the debian package build of julia, I'd like
to request that the debian build process set the TAGGED_RELEASE_BANNER
makefile flag when compiling julia. The identifier string from that flag
will be shown between the version number and the platform triple in the
julia startup banner. Something that identifies the copy of julia as
built in a debian packaging configuration will help us determine whether
reported bugs are due to the debian packaging in particular, if we have
trouble reproducing. I would prefer to have it set in a way that can be
easily (automatically?) overridden by debian derivatives as well.


-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-43-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#816980: [Pkg-julia-devel] Bug#816980: julia: FTBFS in testing (signal (11): Segmentation fault)

[Tony Kelman]

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"  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  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  NIVIRTRESSHR 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.___
> > Pkg-julia-devel mailing list
> > pkg-julia-de...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel
>
>