From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Hyperscan crashes in build process
Date: Thu, 06 Jun 2019 08:26:30 +0100 [thread overview]
Message-ID: <08F2E90C-A6D3-4B2D-9E3F-B181DF563459@ipfire.org> (raw)
In-Reply-To: <a36294af1722d88cb5a97d2c60fcc8ec052a1754.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
How many CPU cores does it have (I assume it is a VM)?
You can disable parallelism then. The build should generally be able to run through with 2GB of RAM because it does that on the ARM boards.
-Michael
> On 6 Jun 2019, at 07:31, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> On Mi, 2019-06-05 at 17:48 +0100, Michael Tremer wrote:
>> Can you upgrade?
> Currently, no.
>
>>
>>> On 5 Jun 2019, at 17:32, ummeegge <ummeegge(a)ipfire.org> wrote:
>>>
>>> On Mi, 2019-06-05 at 17:31 +0100, Michael Tremer wrote:
>>>> How much memory does your build machine have?
>>>
>>> 2GB :-) .
>>>
>>>>
>>>>> 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.c
>>>>> pp.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-06 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01D91B50-AEEA-4706-89A1-98C1F9A074F9@ipfire.org>
2019-06-06 6:31 ` ummeegge
2019-06-06 7:26 ` Michael Tremer [this message]
2019-06-06 17:39 ` ummeegge
2019-06-07 10:11 ` Michael Tremer
2019-06-05 15:40 ummeegge
2019-06-05 16:31 ` 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=08F2E90C-A6D3-4B2D-9E3F-B181DF563459@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