On Thu, Jul 12, 2012 at 5:27 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Thu, Jul 12, 2012 at 12:40:55PM -0300, Ezequiel Garcia wrote
>> Hi,
>>
>> I was trying to emerge gnash but failed. Here's the output....
>>
>> The problem seems to be boost_thread not present. I'll try to emerge
>> that, but in any case this looks like a gentoo bug in gnash ebuild.
>
> Change the jobs option in /etc/make.conf to 1, i.e...
>
> MAKEOPTS="-j1"
>
> You'd be surprised how many "unreproducable" bugs that fixes. I
> simply leave it at that setting all the time. Yes, it takes a little
> bit longer to build, but the compiled binary runs just as fast. And any
> time you "save" building will be lost the first time you spend a few
> hours trying to figure out mysterious build failures.
>

I'll try this and also Michael's suggestion, without re-emerging boost
and let you know.

Thanks guys :-)

On Thu, Jul 12, 2012 at 4:48 PM, Michael Mol <mikemol@gmail.com> wrote:
> On Thu, Jul 12, 2012 at 3:36 PM, Ezequiel Garcia <elezegarcia@gmail.com> wrote:
>> On Thu, Jul 12, 2012 at 3:39 PM, Florian Philipp <lists@binarywings.net> wrote:
>>> Am 12.07.2012 17:40, schrieb Ezequiel Garcia:
>>>> Hi,
>>>>
>>>> I was trying to emerge gnash but failed. Here's the output....
>>>>
>>>> The problem seems to be boost_thread not present. I'll try to emerge
>>>> that, but in any case this
>>>> looks like a gentoo bug in gnash ebuild.
>>>>
>>>> If anyone helps me filling a new bug, I'll appreciate it.
>>>>
>>> [...]
>>>
>>> Could be related to
>>> https://bugs.gentoo.org/show_bug.cgi?id=366407
>>>
>>
>> Thanks!
>>
>> It seems this is a different bug.
>>
>> Before filing a new bug, I should do emerge --sync,
>> (to have latest ebuilds), right?
>
> For me, I'd go:
>
> # In case there's something already broken I don't know about.
> revdep-rebuild
>
> # Remove 'theoretically' unused versions of things.
> emerge --depclean
>
> # Because we ran --depclean, something may now be broken.
> revdep-rebuild
>
> # does an emerge --sync
> eix-sync
>
> # Perhaps specify the particular package, instead of @world
> emerge --update --deep --newuse @world
>

Failed at this point due to boost error (see other boost thread)...

:-(