when i compile mlt-0.2.3 i recieve the following from portage: * QA Notice: The following files contain executable stacks * Files with executable stacks will not work properly (or at all!) * on some architectures/operating systems. A bug should be filed * at http://bugs.gentoo.org/ to make sure the file is fixed. * For more information, see http://hardened.gentoo.org/gnu-stack.xml * Please include this file in your report: * /var/tmp/portage/media-libs/mlt-0.2.3/temp/scanelf-execstack.log * RWX --- --- usr/share/mlt/modules/libmltgtk2.so * QA Notice: Package has poor programming practices which may compil e * fine but exhibit random runtime failures. * producer_vorbis.c:55: warning: implicit declaration of function 'tolower' /var/tmp/portage/media-libs/mlt-0.2.3/temp/scanelf-execstack.log >>> Merging media-libs/mlt-0.2.3 to / there is nothing in /var/tmp/portage/media-libs/mlt-0.2.3/temp/scanelf-execstack.log. Reproducible: Always Steps to Reproduce: 1.emerge mlt-0.2.3 2. 3. Actual Results: i receive this notice Expected Results: i dont know. i read the executable stack website and it is a little too complex. i ran, scanelf -lpeq and the libmltgtk2.so didnt show up. when run kdenlive-0.5(svn) i get random crashing and when did gdb i get many errors like this: #6 0xb7fa8400 in mlt_property_close () from /usr/lib/libmlt.so.0.2.3
I had the same problem with mlt-0.2.4 and I fixed it using: http://www.gentoo.org/proj/en/hardened/gnu-stack.xml by adding the code in Code Listing 6.1 at the end of these two files: src/modules/gtk2/have_mmx.S src/modules/gtk2/scale_line_22_yuv_mmx.S and doing ebuild compile install qmerge. After this I didn't see the crashes I used to when navigating forward in a movie in kdenlive 0.5. Maybe someone could create a patch, put it in the e-build and also submit it upstream to mlt. I never added a patch to an ebuild so I don't want to spend to much time.
Well I still see some crashes, but I think they aren't as frequent.
I can't see any executable stack-related issues with a modern (0.2.4-r2) version of this ebuild. Should this bug really persist today?
These versions are not in Portage anymore, please test >= mlt-0.3.2 and up.
