From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [gentoo-user] bus error during compilation of gcc
Date: Sun, 21 Apr 2013 13:27:28 +0100 [thread overview]
Message-ID: <201304211327.32803.michaelkintzios@gmail.com> (raw)
In-Reply-To: <1366486171.392259470@f315.mail.ru>
[-- Attachment #1: Type: Text/Plain, Size: 701 bytes --]
On Saturday 20 Apr 2013 20:29:31 the guard wrote:
> Суббота, 20 апреля 2013, 15:25 -04:00 от Forrest Schultz
<f.schultz0@gmail.com>:
> > Doesn't lowering makeopts just reduce the number of parallel
> > compilations?
>
> yes, it does. I heard somewhere that bus error is caused by lack of
> sufficient amount of memory during compilations.I also tried to remove
> cflags.
Simplifying cflags to something like:
CFLAGS="-march=native -O2 -pipe"
may help and also setting makeopts to 1:
MAKEOPTS="-j1"
but none of the above will help if the problem is due to a bug. Have you done
the basics like revdep-rebuild and python-updater?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-21 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 17:29 [gentoo-user] bus error during compilation of gcc the guard
2013-04-20 17:54 ` Nilesh Govindrajan
2013-04-20 17:58 ` [gentoo-user] Re[2]: " the guard
2013-04-20 17:59 ` Nilesh Govindrajan
2013-04-20 19:25 ` Forrest Schultz
2013-04-20 19:29 ` [gentoo-user] " the guard
2013-04-21 12:27 ` Mick [this message]
2013-04-25 16:36 ` [gentoo-user] Re[2]: " the guard
2013-04-20 19:56 ` [gentoo-user] " Grant Edwards
2013-04-20 20:44 ` [gentoo-user] " the guard
2013-04-21 19:42 ` Nuno J. Silva (aka njsg)
2013-04-22 6:16 ` [gentoo-user] Re[2]: " the guard
2013-04-22 11:35 ` [gentoo-user] " David Relson
2013-04-22 16:21 ` Nuno J. Silva (aka njsg)
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=201304211327.32803.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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