bug#40789: closed (vigra 1.11.1 build error)

[GNU bug Tracking System]

Your message dated Fri, 24 Apr 2020 16:11:36 -0400
with message-id <address@hidden>
and subject line Re: bug#40789: vigra 1.11.1 build error
has caused the debbugs.gnu.org bug report #40789,
regarding vigra 1.11.1 build error
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
40789: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40789
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: vigra 1.11.1 build error Date: Thu, 23 Apr 2020 08:08:40 +0200

Generation 79   Apr 22 2020 19:23:55    (current)
  guix f916ac1
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: f916ac128a2c4f65f06f6a5148a4862855754d1a

c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[2]: *** 
[vigranumpy/src/core/CMakeFiles/vigranumpy_graphs.dir/build.make:79: 
vigranumpy/src/core/CMakeFiles/vigranumpy_graphs.dir/adjacencyListGraph.cxx.o] 
Error 4
make[2]: *** Waiting for unfinished jobs....

pgpSAF9AwCQs8.pgp
Description: OpenPGP digital signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#40789: vigra 1.11.1 build error
>
>
>
>
> Date: 
>
> Fri, 24 Apr 2020 16:11:36 -0400
>
>
>
>
> On Thu, Apr 23, 2020 at 08:56:39PM +0200, Michael Rohleder wrote:
> > Leo Famulari <address@hidden> writes:
> > > This often means it ran out of memory, which would make sense for
> > > building vigra. Does that seem plausible here?
> > 
> > I think its plausible, because I have *just* build vigra from current
> > master.
>
> Alright, I'm closing the bug.
>
>
> --- End Message ---