On Tue, Oct 15, 2019 at 10:48:06 +0530, Anand Veerappan wrote: > Step 1: As mentioned in your email we remanded the libx264-mv.so.152 file.
You obviously went for the less hacky, but more correct way. > Step 3: While executing FFmpeg binary it requires original libx264.so.152 > instead of modified libx264-mv.so.152. This means that, when ffmpeg was linked, it found a libx264.so with an SONAME of libx264.so.152. So perhaps the libx264.so symlink was pointing at a different libx264.so.XXX (i.e. the original one). - Where is your libx264.so located? Please show the output of ls -l /usr/lib/libx264.so (or to whatever its path is - replace /usr/lib with the actual path please). - Please show us the output of objdump -p /usr/lib/libx264.so.152 | grep SONAME - Please show us the output of objdump -p /usr/lib/libx264-mv.so.152 | grep SONAME > Regards > Anand V BTW, I'm subscribed to the list, that's how I saw your original question. You don't need to Cc: me on your emails. Furthermore, instead of using screenshots of text, just copy and paste text into your email. It's much more efficient and easier to read. Thanks, Moritz _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
