From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Hyperscan crashes in build process
Date: Wed, 05 Jun 2019 17:31:52 +0100 [thread overview]
Message-ID: <99B7B199-39DE-438F-8C53-8E0D7FC28FDE@ipfire.org> (raw)
In-Reply-To: <41f8be54203915ebfc53cec4f1a9927253ae8358.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
How much memory does your build machine have?
> On 5 Jun 2019, at 16:40, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> Hi all,
> just wanted to report that Hyperscan quits in the current origin/next
> build process with
>
> [ 78%] Building CXX object CMakeFiles/hs_compile_shared.dir/src/rose/rose_build_castle.cpp.o
> c++: fatal error: Killed signal terminated program cc1plus
> compilation terminated.
> make[3]: *** [CMakeFiles/hs_compile_shared.dir/build.make:1698: CMakeFiles/hs_compile_shared.dir/src/rose/rose_build_bytecode.cpp.o] Error 1
> make[3]: *** Deleting file 'CMakeFiles/hs_compile_shared.dir/src/rose/rose_build_bytecode.cpp.o'
> make[3]: *** Waiting for unfinished jobs....
> make[3]: Leaving directory '/usr/src/hyperscan-5.1.1'
> make[2]: *** [CMakeFiles/Makefile2:251: CMakeFiles/hs_compile_shared.dir/all] Error 2
> make[2]: Leaving directory '/usr/src/hyperscan-5.1.1'
> make[1]: *** [Makefile:130: all] Error 2
> make[1]: Leaving directory '/usr/src/hyperscan-5.1.1'
> make: *** [hyperscan:80: /usr/src/log/hyperscan-5.1.1] Error 2
>
> Best,
>
> Erik
>
>
>
next prev parent reply other threads:[~2019-06-05 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:40 ummeegge
2019-06-05 16:31 ` Michael Tremer [this message]
[not found] <01D91B50-AEEA-4706-89A1-98C1F9A074F9@ipfire.org>
2019-06-06 6:31 ` ummeegge
2019-06-06 7:26 ` Michael Tremer
2019-06-06 17:39 ` ummeegge
2019-06-07 10:11 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99B7B199-39DE-438F-8C53-8E0D7FC28FDE@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox