in reply to Re: firefox application on 64bit os problem
in thread firefox application on 64bit os problem

WWW::Mechanize::Firefox talks to Firefox using TCP, so there is no problem on that corner. Still it seems very weird to me that the template processing should fail, as all the templates are contained within their respective MozRepl::Plugin modules.

  • Comment on Re^2: firefox application on 64bit os problem

Replies are listed 'Best First'.
Re^3: firefox application on 64bit os problem
by BrowserUk (Patriarch) on Apr 14, 2011 at 16:43 UTC

    Given your authorship, I defer to your expertise. (But if there is any other explanation for that error message, I'd love to know it?:)


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

      It seems that your assumption of the OP mixing 32-bit and 64-bit installation was correct. I didn't look closely enough at the report.

Re^3: firefox application on 64bit os problem
by seven_shen (Acolyte) on Sep 22, 2011 at 08:44 UTC

    I solved the issue finally. The root cause is I use perl-32bit in WIN7-64 platform. The Template::Toolkit module installed in perl 32bit does not support well in WIN7 64bit platform. Thus this $self->template will not get object correctly. After I install perl-64bit and install Template::Toolkit via 64bit-PERL PPM, this issues disappears. So what is the difference between perl 32 and perl 64? Seems most modules installed in 32bit-perl works fine in 64bit OS, but this one is an exception!

      It strikes me as odd that a 32-bit Template::Toolkit should not work on a 32-bit Perl, even on a 64-bit Windows. But maybe you can circumvent the problem by eliminating the XS portions of Template::Toolkit and using the pure-Perl version of Template::Stash...