Bug#652092: Gnash does not handle --enable-avm2
ilatypov at rim.com
Wed Dec 14 18:00:02 UTC 2011
The --enable-avm2 option causes a warning in the configure script saying that the script did not recognize the option. I found that configure.ac commented out its handling by putting "dnl" at the beginning of each line. Removing the "dnl" (delete to new line?) words and removing the build directory gnash-0.8.10~git.master21430, then running "make deb" resulted in a build break,
/bin/bash ../libtool --silent --tag=CXX --mode=compile i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore -I.. -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/librender -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libdevice -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/abc -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/asobj -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/asobj/flash -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/parser -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/vm -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libltdl -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libbase -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libmedia -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libsound -pthread -I/usr/include/glib-2.0
-I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -W -Wall -Wcast-align -Wcast-qual -Wpointer-arith -Wreturn-type -Wnon-virtual-dtor -Wunused -fvisibility-inlines-hidden -c -o DefaultTagLoaders.lo `test -f 'swf/DefaultTagLoaders.cpp' || echo '/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/'`swf/DefaultTagLoaders.cpp
In file included from /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DefaultTagLoaders.cpp:59:0:
/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/SymbolClassTag.h: In member function 'virtual void gnash::SWF::SymbolClassTag::executeActions(gnash::MovieClip*, gnash::DisplayList&) const':
/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/SymbolClassTag.h:48:33: error: 'class gnash::VM' has no member named 'getMachine'
In file included from /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DefaultTagLoaders.cpp:60:0:
/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DoABCTag.h: In member function 'virtual void gnash::SWF::DoABCTag::executeActions(gnash::MovieClip*, gnash::DisplayList&) const':
/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DoABCTag.h:56:33: error: 'class gnash::VM' has no member named 'getMachine'
make: *** [DefaultTagLoaders.lo] Error 1
make: Leaving directory `/home/ilguiz/gnash/gnash-0.8.10~git.master21430/_build/libcore'
It seems that the handling of the option was put away because it did not follow later changes in the code and/or did not agree with those changes.
So I guess addining the --enable-avm2 option to debian/rules did not enable AVM2, and my tests on a flash web site confirm that.
I tried lightspark, but it gave Unsupported ActionScript exception on the "yet unsupported Flash file,"
I wonder if the description of gnash could refer to lightspark as the package extending capabilities of gnash.
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
More information about the pkg-flash-devel