in reply to use PHP::Interpreter throws undefined symbol: zend_ce_traversable

I would hazard a guess that your php libraries are out-of-date or it compiles an .so which is out-dated. That is usually what happens when you see this sort of errors with other perl modules.

  • Comment on Re: use PHP::Interpreter throws undefined symbol: zend_ce_traversable

Replies are listed 'Best First'.
Re^2: use PHP::Interpreter throws undefined symbol: zend_ce_traversable
by Anonymous Monk on Jun 03, 2008 at 06:47 UTC
    I would hazard a guess that your php libraries are out-of-date or it compiles an .so which is out-dated.
    Well, first I tried the stock php from ubuntu (php 5.2.4-2ubuntu5), which gave the above error.

    Then I reverted to the php released prior to the last release of PHP::Interpreter, which was: php-5.0.5 (05 Sep 2005). It failed with the same error: undefined symbol: zend_ce_traversable.

    Then I tried the most recent php from source: php-5.2.6 (01 May 2008). Which also fail in the same way.

    What can I do to resolve the out-date issue?

[reply]
[d/l]

      I could not find anything on Google and zend_ce_traversable definitely looks to be a part of a PHP header file. So the question is where is the error?

      Lets assume that it is not PHP, then it might be the make for the module. That is something that is out of my scope of knowledge. I looked up PHP::Interpeter and the last release is Sep 2005 and noticed that 7 out of 8 system tests fail. I would say that the module itself got broke at some point when PHP was getting updated.

      I am afraid you might be out of look with this module. However, I did a PHP module that might do what you are looking for. It is a little more current in support and passed smoke tests on 5.8.8 on Linux 2.6.22.10.

      Good luck

[reply]
        However, I did a PHP module that might do what you are looking for.
        I assume you mean the PHP module. It allows to embed PHP in Perl. Unfortunately, I want the opposite: Embed Perl in PHP.

        Right now I tend to want to throw away the whole thought a having PHP and Perl coexist on the same setup. Maybe I'll go for Template::Toolkit or something else instead. The reason for wanting PHP in the first place was that it was easier to get PHP people than Perl people.

        BTW: The link under SEE ALSO is broken.

[reply]

In Section Seekers of Perl Wisdom