Hi All: I am one step closer, but still not able to run gnash to play swf file. It seems like my Qt test program running fine with "-qws" flag passed into executable, my directFB test program runs fine as well. So how gnash deal with this situation ? It doesn't honor this argument "-qws".
Thanks chris On Mon, Jun 4, 2012 at 1:54 PM, chris janusz <chrisjanusz...@gmail.com>wrote: > Hi Rob: > Unfortunately, I am cross-compiling for mips platform. I've done some > manual tweaks, after configuration, to make the compilation going. > And now, it finally got compiled. My gui is "Qt", it crashed right after > I typed in "qt4-gnash -h", a little gdb trace showed that jemalloc.c is the > offending one, so i disabled use JEMALLOC flag. > Now, it give me error when I tried to play swf file: > # ./qt4-gnash -v blue.swf -r 1 > QWSSocket::connectToLocalFile could not connect:: No such file or directory > QWSSocket::connectToLocalFile could not connect:: No such file or directory > QWSSocket::connectToLocalFile could not connect:: No such file or directory > QWSSocket::connectToLocalFile could not connect:: No such file or directory > QWSSocket::connectToLocalFile could not connect:: No such file or directory > QWSSocket::connectToLocalFile could not connect:: No such file or directory > No Qt for Embedded Linux server appears to be running. > If you want to run this program as a server, > add the "-qws" command-line option. > Segmentation fault (core dumped) > > Does anybody knows what are needed here? I am not familar with this Qt > stuff, seems like some kind of qt processes must be launched first? > > Thanks > > > On Sun, Jun 3, 2012 at 6:11 PM, Rob Savoye <r...@welcomehome.org> wrote: > >> On 06/01/12 17:11, chris janusz wrote: >> >> > Of course,I also specified lots of "--with-xx-incl=" and >> "--with-xx-lib=" , >> > to tell it where all my libraries are. >> >> Please use Gnash-dev instead of this list. Anyway, you shouldn't >> specify any --with-* options for Gnash on a standard distro. You >> probably overdrove configure. With no --with-* options, Gnash usually >> always does the right thing, so I'd try just './configure' and see what >> happens. >> >> - rob - >> >> >
_______________________________________________ Gnash-dev mailing list Gnash-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnash-dev
