[x264-devel] Possible bug
Wrinkled Cheese
wrinkledcheese at gmail.com
Tue Oct 2 01:44:07 CEST 2012
So you're saying the libx264 configure script automatically decided I
wanted to do all this linking to ffmpeg/libmp3lame? As you can tell from
the options in my post, nothing I explicitly told the libx264 configure
script to do was even remotely linked to ffmpeg or libmp3lame, except maybe
sharing a libdir. The first run through was ./configure && make && sudo
make install with the same errors. The only difference between success and
failure was whether or not I already had ffmpeg and libmp3lame installed.
On Mon, Oct 1, 2012 at 9:33 AM, Jan Ekström <jeebjp at gmail.com> wrote:
> On 2012/10/01 15:31, Jan Ekström wrote:
> > On 2012/10/01 10:06, Wrinkled Cheese wrote:
> >> ...
> >>
> >
> > ...Not that an x264 binary with LAME linked into it would really do
> anything, as it is an encoder and libx264
> > only uses libavformat/libavcodec to decode things...
>
> Whoops, meant /x264/ , not libx264 there.
>
> Jan E
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20121001/2438b9fc/attachment.html>
More information about the x264-devel
mailing list