On Sat, Oct 1, 2011 at 6:26 PM, FeRD <[email protected]> wrote: > > One issue I've noted, in trying to build with the local statically-linked > ffmpeg (the default scenario): the qrender/local_ffmpeg.sh script makes a bad > assumption about the path ffmpeg-snapshot.tar[.bz2] extracts to. (Namely, > that it's NOT 'ffmpeg'.) As a result, it creates a broken recursive symlink > 'ffmpeg/ffmpeg' that eventually breaks the ffmpeg build during its "install" > phase. > > I kluged around that like so (diff attached) — it's admittedly ugly, but it > at least lets the ffmpeg build complete successfully inside qrender/.
...Ugh!! Well, that's just offensive, gmail attaching even the _diff_ as a base64-encoded blob! Sorry about that. Here it is inline, for the sake of being not completely stupid. *sigh* -FeRD --- qrender/local_ffmpeg.sh.orig 2011-09-26 07:41:37.000000000 -0400 +++ qrender/local_ffmpeg.sh 2011-10-01 17:33:50.015000236 -0400 @@ -189,11 +189,16 @@ bzip2 -d $theFile theFile=`basename $theFile .bz2` extractDir=`tar --list -f $theFile | grep INSTALL | sed "s/\\/INSTALL$//"` + if [ -d $extractDir ]; then + rm -r $extractDir + fi; tar -xf $theFile - if [ -e ffmpeg ]; then - rm ffmpeg + if [ "x$extractDir" != "xffmpeg" ]; then + if [ -e ffmpeg ]; then + rm ffmpeg + fi; + ln -s "$extractDir" ffmpeg fi; - ln -s "$extractDir" ffmpeg fi; cd ffmpeg ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ QDVDAuthor-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qdvdauthor-users
