1 |
On Thu, Jul 12, 2012 at 3:36 PM, Ezequiel Garcia <elezegarcia@×××××.com> wrote: |
2 |
> On Thu, Jul 12, 2012 at 3:39 PM, Florian Philipp <lists@×××××××××××.net> wrote: |
3 |
>> Am 12.07.2012 17:40, schrieb Ezequiel Garcia: |
4 |
>>> Hi, |
5 |
>>> |
6 |
>>> I was trying to emerge gnash but failed. Here's the output.... |
7 |
>>> |
8 |
>>> The problem seems to be boost_thread not present. I'll try to emerge |
9 |
>>> that, but in any case this |
10 |
>>> looks like a gentoo bug in gnash ebuild. |
11 |
>>> |
12 |
>>> If anyone helps me filling a new bug, I'll appreciate it. |
13 |
>>> |
14 |
>> [...] |
15 |
>> |
16 |
>> Could be related to |
17 |
>> https://bugs.gentoo.org/show_bug.cgi?id=366407 |
18 |
>> |
19 |
> |
20 |
> Thanks! |
21 |
> |
22 |
> It seems this is a different bug. |
23 |
> |
24 |
> Before filing a new bug, I should do emerge --sync, |
25 |
> (to have latest ebuilds), right? |
26 |
|
27 |
For me, I'd go: |
28 |
|
29 |
# In case there's something already broken I don't know about. |
30 |
revdep-rebuild |
31 |
|
32 |
# Remove 'theoretically' unused versions of things. |
33 |
emerge --depclean |
34 |
|
35 |
# Because we ran --depclean, something may now be broken. |
36 |
revdep-rebuild |
37 |
|
38 |
# does an emerge --sync |
39 |
eix-sync |
40 |
|
41 |
# Perhaps specify the particular package, instead of @world |
42 |
emerge --update --deep --newuse @world |
43 |
|
44 |
# Again, remove old versions of things. |
45 |
emerge --depclean |
46 |
|
47 |
# Again, because --depclean can break things. |
48 |
revdep-rebuild |
49 |
|
50 |
...and then see if I can reproduce it. |
51 |
|
52 |
> I wonder why they've used boost! (I'm not a big fan of it) |
53 |
|
54 |
Boost probably had some code in it they didn't want to reinvent |
55 |
themselves. It's also pretty common, which makes things easier for a |
56 |
developer who wants to get into more distributions' repositories. |
57 |
|
58 |
-- |
59 |
:wq |