From: johnstrass <johnstrass@163.com>
To: gentoo-user@lists.gentoo.org, lperkins@openeye.net,
dmf@fellowsandcarr.ca
Subject: Re:RE: [gentoo-user] gcc 12.1.1 compile error on loongson2f Yeeloong
Date: Sat, 30 Jul 2022 17:51:20 +0800 (CST) [thread overview]
Message-ID: <57b2f5c8.19c9.1824e8477b4.Coremail.johnstrass@163.com> (raw)
In-Reply-To: <MW2PR07MB4058F180AF01AD5050F77675D2999@MW2PR07MB4058.namprd07.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3264 bytes --]
Thank you very much! I will give it a try.
At 2022-07-30 02:29:14, "Laurence Perkins" <lperkins@openeye.net> wrote:
>Turning on zswap or, better yet, setting up a zram swap with a file to back it helps quite a bit on swapping since a lot of the data in question is highly compressible.
>
>Additionally, disable the "pipe" compiler option in make.conf so that it writes intermediate files out to disk instead of trying to keep them in memory.
>
>And finally, if you have a more powerful machine sitting around, look into distcc and/or setting up a binhost. You'll be much happier in the long-run.
>
>LMP
>
>-----Original Message-----
>From: David M. Fellows <dmf@fellowsandcarr.ca>
>Sent: Friday, July 29, 2022 7:50 AM
>To: gentoo-user@lists.gentoo.org; johnstrass <johnstrass@163.com>
>Subject: Re: [gentoo-user] gcc 12.1.1 compile error on loongson2f Yeeloong
>
>>Dear friends, I am updating the gentoo mip-n32 system on my Yeeloong
>>netbook. During updating of the @world, it began to update the gcc
>>12.1.1 from gcc 11.3.0 which is also the one doing the compilation. And
>>after a long-time compilation, it stops with error messages: " ......
>
>Hmm. 1G ram and 1G swap is not much memory for building gcc.
>You could check dmesg and syslog for out-of memory kill messages occurring during your builds.
>
>It would be easy to try again specifying MAKEOPTS="-j1". Also make sure that you have no unnecesary other processes running during the build - especially memory hogs like a web browser.
>
>You could add swap, but if you are doing much swapping it will be intolerably slow.
>
>I would also arrange for some extra cooling of the laptop just in the load is causing overheating.
>
>DaveF
>
>>
>>
>>rm gfdl.pod gcc.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod
>>cpp.pod gcov.pod lto-dump.pod make[2]: *** [Makefile:5000:
>>all-stage2-gcc] Error 2 make[1]: *** [Makefile:22474: stage2-bubble]
>>Error 2 make: *** [Makefile:22697: bootstrap-lean] Error 2 * ERROR:
>>sys-devel/gcc-12.1.1_p20220625::gentoo failed (compile phase): * emake
>>failed * * If you need support, post the output of `emerge --info
>>'=sys-devel/gcc-12.1.1_p20220625::gentoo'`, * the complete build log
>>and the output of `emerge -pqv '=sys-devel/gcc-12.1.1_p20220625::gentoo'`.
>>* The complete build log is located at
>>'/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/temp/build.log'.
>>* The ebuild environment file is located at
>>'/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/temp/environment'.
>>* Working directory:
>>'/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/work/build' * S:
>>'/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/work/gcc-12-20220625'
>>* Please include
>>/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/work/gcc-build-logs.tar.
>>bz2 in your bug report. *
>>
>>
>>>>> Failed to emerge sys-devel/gcc-12.1.1_p20220625, Log file:
>>
>>
>>>>> '/var/tmp/portage/sys-devel/gcc-12.1.1_p20220625/temp/build.log' "
>>>>> I
>>also tried to emerge 11.3.1, but it still stoped at the compile stage.
>>But I forgot to save the enviroment.
>>
>>
>>Any help? The necessary log files are attached. Thanks.
>>>> application/x-gzip attachment, name=buildlogs-12.1.1.tar.gz
>>>> application/x-gzip attachment, name=buildlogs-11.3.1.tar.gz
>
[-- Attachment #2: Type: text/html, Size: 3777 bytes --]
prev parent reply other threads:[~2022-07-30 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 12:57 [gentoo-user] gcc 12.1.1 compile error on loongson2f Yeeloong johnstrass
2022-07-29 14:50 ` David M. Fellows
2022-07-29 18:29 ` Laurence Perkins
2022-07-30 9:51 ` johnstrass [this message]
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=57b2f5c8.19c9.1824e8477b4.Coremail.johnstrass@163.com \
--to=johnstrass@163.com \
--cc=dmf@fellowsandcarr.ca \
--cc=gentoo-user@lists.gentoo.org \
--cc=lperkins@openeye.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox