On 21/08/2015 04:41, wraeth wrote:
> On 21/08/15 11:49, Alan Grimes wrote:
>> tortoise ~ # emerge --info ... Repositories:
>
> You have a fair number of overlays. It probably doesn't need to be
> said, but you should watch out for packages being pulled in from an
> overlay instead of the default Gentoo repository.
>
>> CFLAGS="-O3 -march=native -pipe " CXXFLAGS="-O3 -march=native -pipe
>> "
>
> C{XX}FLAGS="-O3" is known to cause some issues [1]. If you've done an
> --emptytree rebuild with "-O3" then this could be the cause of the
> segfaults.
Earlier I saw segfaults in gcc, and another poster pointed it out.
When gcc segfaults, it is always suspicious mostly because the compiler
is an app where we know the devs take extraordinary measures to prevent it.
The most common cause is faulty hardware (most often memory) as gcc
tends to use all of it in ways no other app does. The usual procedure at
this point is to run memtest for an extended period - say 48 hours, or
even 72 for an older slow machine.
>
>> wraeth wrote:
>>> More information about your environment, such as an `emerge
>>> --info` and relevant flags/settings for a specific package that
>>> is failing would go a fair way to giving us the information we
>>> need (and have asked for) to be able to help you.
>
> The `emerge --info` helps, but you haven't listed an explicit build
> failure or details about that package.
>
--
Alan McKinnon
alan.mckin...@gmail.com
