Summary: | k3b-1.93.0/b has linker error /usr/bin/ld: /usr/local/lib/libavcodec.a | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | BrianP <brianp> |
Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | adaptee, michalm, trueg |
Priority: | NOR | ||
Version First Reported In: | 1.93.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
BrianP
2010-06-18 19:58:17 UTC
A failing build is not a "crash", but just a build failure. Also, /usr/local/lib/libavcodec.a looks like you compiled your own libavcodec, and there is no shared library (.so) version of it, but it was compiled as static library. Please check that you have also the shared library version, and if not check whether you can compile libavcodec in such way. Pino, /usr/local/lib/libavcodec.a was installed with Synaptic and is Ubuntu 10.04 standard. I did try to compile ffmpeg from source, but it also has build errors which I never could figure out. Try k3b on a stock, minimal ubu 10/04. No worky. 9.10 does work. K3b and ffmpeg folks need to make sure their stuff builds at the OS level, not just at the bench level. :) Brian On 06/21/2010 12:06 PM, Pino Toscano wrote: > https://bugs.kde.org/show_bug.cgi?id=242101 > > > Pino Toscano<pino@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Severity|crash |normal > > > > > --- Comment #1 from Pino Toscano<pino kde org> 2010-06-21 19:06:46 --- > A failing build is not a "crash", but just a build failure. > Also, /usr/local/lib/libavcodec.a looks like you compiled your own libavcodec, > and there is no shared library (.so) version of it, but it was compiled as > static library. Please check that you have also the shared library version, and > if not check whether you can compile libavcodec in such way. > Feel free to reopen the report and paste backtrace if the problem still happens in recent versions |