1 |
Well, you need to re-emerge libtool only if you have upgraded gcc |
2 |
(even 4.4.3->4.4.4). Tomorrow I will try to commit some ebuild for |
3 |
testing, to have at least hacked & working akode ebuild until we |
4 |
figure out the correct way. |
5 |
|
6 |
On 8/28/10, Brent Busby <brent@×××××××××.org> wrote: |
7 |
> On Sat, 28 Aug 2010, Duncan wrote: |
8 |
> |
9 |
>> Ladislav Laska posted on Fri, 27 Aug 2010 22:28:54 +0200 as excerpted: |
10 |
>> |
11 |
>>> Unfortunately, we can't use this hack in ebuild, since it requires |
12 |
>>> libtool rebuild in most cases. |
13 |
>> |
14 |
>> No longer a kde3 user, but... |
15 |
>> |
16 |
>> One thing you /could/ do (maybe it's there already?) is to put something |
17 |
>> in the messages about trying a libtool remerge if merging akode fails |
18 |
>> (maybe if it fails with a specific error), before trying anything else. |
19 |
>> |
20 |
>> I've seen other ebuilds do that... |
21 |
> |
22 |
> The thing is, I'm not sure in what circumstances I'd have to be in for |
23 |
> that to work for me. I've already tried just remerging libtool. Would |
24 |
> I have to remerge gcc too? (This machine has always used gcc 4.4.) |
25 |
> |
26 |
> -- |
27 |
> + Brent A. Busby + "We've all heard that a million monkeys |
28 |
> + UNIX Systems Admin + banging on a million typewriters will |
29 |
> + University of Chicago + eventually reproduce the entire works of |
30 |
> + Physical Sciences Div. + Shakespeare. Now, thanks to the Internet, |
31 |
> + James Franck Institute + we know this is not true." -Robert Wilensky |
32 |
> |
33 |
> |
34 |
|
35 |
|
36 |
-- |
37 |
Regards Ladislav Laska |
38 |
S pozdravem Ladislav Laska |
39 |
--- |
40 |
xmpp/jabber: ladislav.laska@××××××.cz |