| 1 |
On 10/16/2009 04:37 AM, Neil Bothwick wrote: |
| 2 |
> On Fri, 16 Oct 2009 12:20:30 +0100, Peter Humphrey wrote: |
| 3 |
> |
| 4 |
>> I thought I'd have a play with swami, but the emerge fails with |
| 5 |
>> "/bin/sed: can't read /usr/lib64/libogg.la: No such file or directory", |
| 6 |
>> and indeed there is none such. |
| 7 |
> |
| 8 |
> The elog message from the last libogg install explains this. Run |
| 9 |
> lafilefixer --justfixit. |
| 10 |
|
| 11 |
There is no manpage for lafilefixer, but the --help flag prints: |
| 12 |
|
| 13 |
--justfixit Choose some reasonable dirs, such as /usr/lib*, etc. , |
| 14 |
find all .la files and fix them to not use .la files |
| 15 |
for linking |
| 16 |
|
| 17 |
I can't make sense out of that -- one of the major uses of libtool (I thought) |
| 18 |
is for linking. Can anyone 'splain that to me? |
| 19 |
|
| 20 |
Thanks. |
Archives