From: swedebugia <swedebugia@riseup.net>
To: Guillaume LE VAILLANT <glv@posteo.net>
Cc: 36258@debbugs.gnu.org
Subject: [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0.
Date: Sun, 23 Jun 2019 13:31:23 +0200 [thread overview]
Message-ID: <f386089a-566f-6d0d-3f2e-6e7036c2a27a@riseup.net> (raw)
In-Reply-To: <87imsx2rk3.fsf@yamatai>
On 2019-06-23 00:17, Guillaume LE VAILLANT wrote:
>
> swedebugia a écrit :
>
>> I tried building it with 4GB ram and 4GB swap but it failed with this error
>> which I suspect is memory-related.
>>
>> I'm building it again now with -c 1 and it got past this point :) I will review
>> further once it is done.
>>
>> make -f src/wallet/CMakeFiles/obj_wallet.dir/build.make
>> src/wallet/CMakeFiles/obj_wallet.dir/build
>> make[2]: Entering directory '/tmp/guix-build-monero-0.14.1.0.drv-0/build'
>> [ 32%] Building CXX object src/wallet/CMakeFiles/obj_wallet.dir/wallet2.cpp.o
>>
>> [...]
>>
>> c++: internal compiler error: Killed (program cc1plus)
>
> Yes I think it's a crash caused by an "out of memory" error. The
> wallet2.cpp file is pretty big (around 500 kB), and apparently g++ wants
> several gigabytes of RAM to compile it. When compiling on my system with
> 8 threads, 16 GB of RAM and 8 GB of swap, I often saw between 3 and 4 GB
> being swapped when the compiling process got to that file.
>
It finished compiling on 1 core but the tests stopped after an hour and
was completely silent and no cpu use.
How do I run the tests manually?
I tried:
cd into /tmp/guix-build-xxx
source the env
cd build
make "ARGS=-R 'hash|core_tests'" "test"
but got this error:
Could not find executable
/tmp/guix-build-monero-0.14.1.0.drv-0/build/tests/hash-target-tests
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-06-23 11:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 8:44 [bug#36258] [PATCH 1/2] gnu: monero: Update to 0.14.1.0 Guillaume LE VAILLANT
2019-06-17 8:44 ` [bug#36259] [PATCH 2/2] gnu: monero-gui: " Guillaume LE VAILLANT
2019-06-26 12:08 ` Guillaume LE VAILLANT
2019-06-26 22:55 ` swedebugia
2019-07-03 10:07 ` bug#36259: " Ludovic Courtès
2019-06-22 20:38 ` [bug#36258] [PATCH 1/2] gnu: monero: " swedebugia
2019-06-22 22:17 ` Guillaume LE VAILLANT
2019-06-23 11:31 ` swedebugia [this message]
2019-06-23 12:53 ` Guillaume LE VAILLANT
2019-06-23 13:18 ` swedebugia
2019-06-24 6:20 ` swedebugia
2019-06-24 9:54 ` Guillaume LE VAILLANT
2019-06-25 10:07 ` Guillaume LE VAILLANT
2019-06-25 11:32 ` swedebugia
2019-07-03 10:06 ` bug#36258: " Ludovic Courtès
2019-07-14 11:11 ` [bug#36258] " swedebugia
2019-07-14 11:51 ` Guillaume Le Vaillant
2019-07-14 13:32 ` Ludovic Courtès
2019-07-14 14:55 ` swedebugia
2019-07-14 16:13 ` Guillaume Le Vaillant
2019-07-15 10:50 ` Ludovic Courtès
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=f386089a-566f-6d0d-3f2e-6e7036c2a27a@riseup.net \
--to=swedebugia@riseup.net \
--cc=36258@debbugs.gnu.org \
--cc=glv@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.