Project

Profile

Help

Bug #5241

closed

PHP API for Saxon/C HE for PHP version 8.

Added by Abhiroop Ghosh 11 months ago. Updated about 2 months ago.

Status:
Duplicate
Priority:
Normal
Category:
PHP Build
Start date:
2022-01-26
Due date:
% Done:

0%

Estimated time:
Found in version:
Fixed in version:
Platforms:

Description

The php installation on Linux server supports PHP 7 at present. Can we run PHP 8 with this Saxon/C HE version. The commands provided for PHP 7 installation on reference link (https://www.saxonica.com/saxon-c/documentation1.2/index.html#!starting/installingphp) it mentions about building with PHP 7 and PHP 5 but the code structure is a bit different for PHP 8. Attaching the configuration settings for the server. Is there any way to install the Saxon for PHP 8. Getting issues with using SaxonProcessor() class for running Xpaths in php code as the class is not available.


Files

php-linux-config-image.png (72.3 KB) php-linux-config-image.png Abhiroop Ghosh, 2022-01-26 17:13

Related issues

Related to SaxonC - Feature #4842: PHP 8AwaitingInfoO'Neil Delpratt2020-11-26

Actions
Actions #1

Updated by O'Neil Delpratt 11 months ago

  • Project changed from Saxon to SaxonC
  • Category changed from Configuration to PHP Build
Actions #2

Updated by O'Neil Delpratt 11 months ago

PHP 8 is not currently supported in Saxon/C. I did revisit this issue today and can see a number of compile failures when I tried to build SaxonC for PHP 8. We are pushing out the new SaxonC 11 release soon. Once this is out I will work on getting SaxonC supported on PHP 8.

Actions #3

Updated by O'Neil Delpratt 9 months ago

Sorry for dropping the ball on this feature request. We will look at this shortly

Actions #4

Updated by O'Neil Delpratt 9 months ago

Actions #5

Updated by O'Neil Delpratt about 2 months ago

  • Status changed from New to Duplicate
  • Assignee changed from Community Admin to O'Neil Delpratt

I have made some progress with getting SaxonC to work on PHP 8.1. I am reporting progress here #4842, therefore I am marking this bug issue as a duplicate.

Please register to edit this issue

Also available in: Atom PDF