Re: soname bumps: faad2-2.7 and x264

On Sunday, 22 March 2009 at 16:35, Dominik 'Rathann' Mierzejewski wrote: > On Saturday, 21 March 2009 at 20:12, Dominik 'Rathann' Mierzejewski wrote: > > Hi. > > > > Over the past couple of weeks I've been mock-rebuilding rawhide packages > > against current x264 and faad2-2.7, both of which bring ABI and API changes. > > > > Here's the list of affected packages with current status of my rebuilds: > > > > - = untested, + = rebuilt fine, * = rebuilt after fixes, X = failed, unfixed > > > > for faad2: > > X avidemux > > + cmus > > + ffmpeg > > * gpac > > X gstreamer-plugins-bad > > * libquicktime > > + mpd > > + mplayer > > - mythtv > > + streamripper > > X vlc > > + xine-lib-extras-freeworld > > + xmms2-freeworld > > > > for x264: > > X avidemux > > + ffmpeg > > X gstreamer-plugins-bad > > * libquicktime > > + mencoder (mplayer) > > X vlc > > > > Reports for gpac and libquicktime have been posted to bugzilla. > > I'll keep poking at avidemux, gstreamer and vlc. > > Status update: > gstreamer-plugins-bad and vlc are now building fine (fixes posted in bugzilla). > avidemux compiles fine but fails on translation files (bugs filed/updated). And current mythtv from rawhide seems to build fine against faad2-2.7. I wonder though why it is dlopen()ing the library instead of simply linking to it?