Project

Profile

Help

Support #5137

Unable to build Saxon EE/C 1.2.1 and HE/C 1.2.1 as a PHP 5 extension

Added by Christina Spies about 1 month ago. Updated about 1 month ago.

Status:
AwaitingInfo
Priority:
Low
Category:
PHP Build
Start date:
2021-10-19
Due date:
% Done:

0%

Estimated time:
Found in version:
1.2.1
Platforms:

Description

I've been trying to build Saxon-EE/C 1.2.1 as an extension for PHP 5.6.38 in a 64-bit version of Puppy Linux.

I think it probably almost worked, but there were some errors with the "make" command (which didn't finish compiling) and the "configure" command (which seemed to run successfully despite the errors).

Those errors are shown below, and also in the attached file "EEC-1.2.1-build-transcript.txt".

I also tried building Saxon HE/C 1.2.1 mostly the same way (except a different installation path and SAXONC_HOME path), and had similar errors. (Included in the attached file "HEC-1.2.1-build-transcript.txt".)

I'm very unfamiliar with C and C++, so, despite trying, I was unable to fix the problems myself.


A few years ago, I was able to successfully build PHP 5.6.38 extensions of Saxon-HE/C 1.1.0 (with [your assistance](https://saxonica.plan.io/issues/4030) - thanks again!) and Saxon-HE/C 1.0.2 on this same computer, so I'm optimistic that Saxon-EE/C 1.2.1 and Saxon-HE/C 1.2.1 can probably also work on this computer, even though I'm still using an increasingly old OS - the Lighthouse 64 6.02 Beta 2 version of Puppy Linux, released in 2013.

Happily, I already have Saxon-EE 10.6 for Java working fine on this computer, and I love it!

So, I'm not in any rush here - I could probably get by with that alone if I had to. But I have a lot of legacy PHP 5 software I'm stuck with for now, so it would be nice (though not urgent or essential) for me to be able to use Saxon EE/C 1.2.1 as a PHP 5 extension.

Thanks for any help!


Here's a description of what I did to try to build Saxon-EE/C 1.2.1:
  • I unzipped "libsaxon-EEC-setup64-v1.2.1.zip" into this folder:

/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC


  • Then, I went there and ran this:

./libsaxon-EEC-setup64-v1.2.1


  • I installed it with the default destination path it gave me:

/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1

I attached the install.log file as "EEC-1.2.1-install.log", in case it might help.


  • Then I set the environment variable SAXONC_HOME by adding this line to the file "/etc/profile.log":

export SAXONC_HOME="/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1"


Quote:

The use of symbolic links to specify where the Saxon/C library is installed is no longer recommended. It is better to set the SAXONC_HOME environment variable directly.


  • I removed the old symlinks I had to Saxon-HE/C 1.0.2's "rt" folder and "libsaxonhec.so".

  • In the "Saxon.C.API" folder, I overwrote "config.m4" with "PHP5-Build/config.m4".

  • I ran this:

phpize

Which produced this successful-looking output:

bash-4.1# phpize
Configuring for:
PHP Api Version:         20131106
Zend Module Api No:      20131226
Zend Extension Api No:   220131226

  • Then I ran:

./configure --enable-saxon --prefix "/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1"

Which seemed to run successfully despite a few errors:

bash-4.1# ./configure --enable-saxon --prefix "/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1"
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
expr: syntax error
./configure: line 2599: test: =: unary operator expected
expr: syntax error
./configure: line 2605: test: =: unary operator expected
expr: syntax error
./configure: line 2612: test: =: unary operator expected
expr: syntax error
./configure: line 2605: test: =: unary operator expected
expr: syntax error
./configure: line 2612: test: =: unary operator expected
expr: syntax error
./configure: line 2605: test: =: unary operator expected
expr: syntax error
./configure: line 2612: test: =: unary operator expected
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for PHP prefix... /root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk
checking for PHP includes... -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/main -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/TSRM -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/Zend -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext/date/lib
checking for PHP extension directory... /root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/lib/php/extensions/no-debug-non-zts-20131226
checking for PHP installed headers prefix... /root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... gawk
checking Whether to enable the "saxon" extension... yes, shared
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by cc... /usr/x86_64-slackware-linux/bin/ld
checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/x86_64-slackware-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no

creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/x86_64-slackware-linux/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
configure: creating ./config.status
config.status: creating config.h

  • I edited "Makefile" since I keep Java in an unconventional location. (And also because this step was needed years ago when I successfully built HE/C 1.02 and HE/C 1.10 on this same computer.)

I changed line 31, which said:

CPPFLAGS = -DHAVE_CONFIG_H

...to this:

CPPFLAGS = -DHAVE_CONFIG_H -I/root/apbin/Java/v8u51/include/ -I/root/apbin/Java/v8u51/include/linux/ -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1


  • Lastly, I ran:

make

Which had the below errors:

/bin/sh /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/libtool --mode=compile g++  -I. -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API -DPHP_ATOM_INC -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/include -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/main -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/main -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/TSRM -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/Zend -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext/date/lib -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/jni  -DHAVE_CONFIG_H -I/root/apbin/Java/v8u51/include/ -I/root/apbin/Java/v8u51/include/linux/ -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1  -g -O2   -c /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp -o php5_saxon.lo 
mkdir .libs
 g++ -I. -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API -DPHP_ATOM_INC -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/include -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/main -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/main -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/TSRM -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/Zend -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext -I/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/include/php/ext/date/lib -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/jni -DHAVE_CONFIG_H -I/root/apbin/Java/v8u51/include/ -I/root/apbin/Java/v8u51/include/linux/ -I/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1 -g -O2 -c /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp  -fPIC -DPIC -o .libs/php5_saxon.o
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:20:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:20:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp: In function 'void zim_SaxonProcessor_isSchemaAware(int, zval*, zval**, zval*, int)':
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:543:55: error: return-statement with a value, in function returning 'void' [-fpermissive]
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:546:13: error: return-statement with a value, in function returning 'void' [-fpermissive]
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp: In function 'void zim_Xslt30Processor_transformToString(int, zval*, zval**, zval*, int)':
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2472:66: error: no matching function for call to 'Xslt30Processor::transformToString()'
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2472:66: note: candidate is:
In file included from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/SaxonProcessor.h:36:0,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.h:41,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:5:
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:462:18: note: const char* Xslt30Processor::transformToString(XdmNode*)
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:462:18: note:   candidate expects 1 argument, 0 provided
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp: In function 'void zim_Xslt30Processor_transformToValue(int, zval*, zval**, zval*, int)':
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2503:54: error: no matching function for call to 'Xslt30Processor::transformToValue()'
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2503:54: note: candidate is:
In file included from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/SaxonProcessor.h:36:0,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.h:41,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:5:
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:471:16: note: XdmValue* Xslt30Processor::transformToValue(XdmNode*)
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:471:16: note:   candidate expects 1 argument, 0 provided
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp: In function 'void zim_Xslt30Processor_transformToFile(int, zval*, zval**, zval*, int)':
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2539:35: error: no matching function for call to 'Xslt30Processor::transformToFile()'
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:2539:35: note: candidate is:
In file included from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/SaxonProcessor.h:36:0,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.h:41,
                 from /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/php5_saxon.cpp:5:
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:482:10: note: void Xslt30Processor::transformToFile(XdmNode*)
/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.2.1-EEC/Saxonica/SaxonEEC1.2.1/Saxon.C.API/Xslt30Processor.h:482:10: note:   candidate expects 1 argument, 0 provided
make: *** [php5_saxon.lo] Error 1

Thanks again for any help!

EEC-1.2.1-build-transcript.txt (71.8 KB) EEC-1.2.1-build-transcript.txt Christina Spies, 2021-10-19 23:44
EEC-1.2.1-install.log (273 KB) EEC-1.2.1-install.log Christina Spies, 2021-10-19 23:45
HEC-1.2.1-build-transcript.txt (69.8 KB) HEC-1.2.1-build-transcript.txt Christina Spies, 2021-10-19 23:45
HEC-1.2.1-install.log (264 KB) HEC-1.2.1-install.log Christina Spies, 2021-10-19 23:45

History

#1 Updated by O'Neil Delpratt about 1 month ago

  • Category set to PHP Build
  • Assignee set to O'Neil Delpratt
  • Found in version changed from Saxon-EE/C 1.2.1; Saxon-HE/C 1.2.1 to 1.2.1

Hi,

Thanks for reporting the issue you have found. Please check out the following bug issue which may have a solution to your problem: https://saxonica.plan.io/issues/4271

In that bug issue I created a build for PHP5 which you can download and use. See: https://dev.saxonica.com/repos/archive/opensource/latest9.8/hec/php-library-module/php5/64-bit/HEC/saxon.so

#2 Updated by O'Neil Delpratt about 1 month ago

  • Status changed from New to AwaitingInfo

#3 Updated by Christina Spies about 1 month ago

Thank you so much! Following the instructions from post #2 of the page you pointed out - https://saxonica.plan.io/issues/4271#note-2 - enabled me to compile both Saxon-EE/C 1.1.2 and Saxon-HE/C 1.1.2 successfully.

I tried the same fix with 1.2,1, but the faulty line in 1.1.2's "php5_saxon.cpp" file appears to have been fixed already in both EE/C 1.2.1 and HE/C 1.2.1. So, I still haven't been able to build those.

I'll happily try new possible fixes whenever they become available.

In the meanwhile, I believe EE/C 1.1.2 and Saxon-EE 10.6 will probably be completely sufficient for my purposes, which at this point mostly consist of learning a lot more about XSLT.

I'm definitely excited about the ability in 1.2.1 to use extension functions written in PHP, but there are still plenty of XSLT basics I'm guessing should probably learn first. :-)

Thanks again!

#4 Updated by Christina Spies about 1 month ago

Additional notes for anyone who might be trying to install Saxon EE/C 1.1.2 or HE/C 1.1.2:

To build 1.1.2, I used mostly the same build process I described above for EE/C 1.2.1, with the differences that with this earlier version, I had to put symlinks to the "rt" folder and "libsaxoneec.so" (or "libsaxonhec.so") in /usr/lib.

And I added this line to the file "/etc/profile.local":

export LD_LIBRARY_PATH=/usr/lib/rt/lib/i386:$LD_LIBRARY_PATH

In my PHP installation's extension folder, which I keep at this unconventional location:

/root/apbin/APSK-GLMP-GTK/PHP/v5.6.38-glmp-gtk/lib/php/extensions/no-debug-non-zts-20131226

...I put symlinks to:

/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.1.2-EEC/Saxonica/Saxon-EEC1.1.2/Saxon.C.API/modules/saxon.la /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.1.2-EEC/Saxonica/Saxon-EEC1.1.2/Saxon.C.API/modules/saxon.so

Or, in the case of HE/C 1.1.2:

/root/apbin/APSK-GLMP-GTK/Saxon-C/v1.1.2-HEC/Saxonica/Saxon-HEC1.1.2/Saxon.C.API/modules/saxon.la /root/apbin/APSK-GLMP-GTK/Saxon-C/v1.1.2-HEC/Saxonica/Saxon-HEC1.1.2/Saxon.C.API/modules/saxon.so

I got the EE-only schema features working by placing my license file in both my $SAXONC_HOME folder and /usr/lib.

#5 Updated by O'Neil Delpratt about 1 month ago

  • Status changed from AwaitingInfo to Resolved

Hi,

Glad you got the Saxon/C PHP5 extension to build.

For the next release of Saxon/C we are considering dropping support for PHP5. What are your thoughts if any as a user of Saxon/C on this move? And generally are there many users out there still using PHP5?

#6 Updated by O'Neil Delpratt about 1 month ago

  • Status changed from Resolved to AwaitingInfo

#7 Updated by Christina Spies about 1 month ago

Quoted from post #5, https://saxonica.plan.io/issues/5137?pn=1#note-5 -

And generally are there many users out there still using PHP5?

Off the top of my head, I actually don't know. I'm currently an amateur hobbyist free/libre/open source programmer who doesn't stay very informed about the tech industry, though I do hope to start a profitable (but still libre/open source) business someday when my creations seem ready enough for that.

What I do know (without googling anything yet) is that PHP 5 was definitely enormously popular in its day.

I wouldn't be too surprised if still is in common use - even on web servers on the internet, though I doubt that's wise from a security perspective. (But I'm definitely no security expert.)


This old article from Oct. 2018 - [[https://threatpost.com/as-end-of-life-nears-more-than-half-of-websites-still-use-php-v5/138352/]] - says "Support for PHP 5.6 drops on December 31 – but a recent report found that almost 62 percent of websites are still using version 5."

This more recent page - [[https://w3techs.com/technologies/history_details/pl-php/5]] - titled "Historical trends in the usage statistics of PHP version 5 for websites" - actually says that usage of PHP 5.6 has actually only gone UP from Oct. 2020 to Oct. 2021!

It started at 52.2% in Oct. 2020, and went up to 56.1% by Oct. 2021!

I have no way to judge how accurate that is, but, that is very interesting, particularly if true.



I have overall little experience with PHP 7 and 8, so I don't know if people are fleeing from them because they're somehow intolerable compared to PHP 5.6.x.

But I can definitely understand simply not wanting to upgrade things unless it's absolutely necessary.

#8 Updated by Christina Spies about 1 month ago

Quoted from post #5, https://saxonica.plan.io/issues/5137?pn=1#note-5 -

For the next release of Saxon/C we are considering dropping support for PHP5. What are your thoughts if any as a user of Saxon/C on this move?

I don't know how difficult it would be to keep PHP 5 support, but it would be understandable if you drop support for it, especially if it would be difficult.

According to this page - [[https://www.php.net/releases/index.php]] - even the makers of PHP discontinued support for PHP 5 since Jan. 10, 2019.

But on the other hand, if the statistics page mentioned above - [[https://w3techs.com/technologies/history_details/pl-php/5]] - is right, PHP 5 appears to still be incredibly popular.



I'm generally happy to use even practically antique software as long as it still does what I need - unless there are serious security concerns to worry about.

Again, I'm definitely no security expert, but even I would be reluctant to use PHP 5 forever on a web server that is actually connected to the internet.

However, I'm often happy to use such software inside a VirtualBox with no internet access. That's what I do with a lot of my self-written legacy PHP 5 programs, except the ones that don't even need a web server or database server.



PHP (any version) is probably most commonly used for web development, but I actually use PHP 5 mostly for local desktop programs that don't involve the internet at all.

I'm not sure how common that is, but, there are definitely at least a few other people than me who like the desktop software PHP-GTK, which still only runs with PHP 5.

Here's my favorite website about PHP-GTK: https://www.kksou.com/php-gtk2/category/Sample-Codes



Currently, the only things tying me to PHP 5 are:

  • My own self-written PHP 5 software, which has been too much of a nuisance for me to update.

  • I haven't yet figured out how to get PHP-GTK working with versions of PHP later than 5.6.x, and there doesn't seem to be much community interest in doing so, judging by the mostly quiet PHP-GTK mailing list. (But I'm certainly interested enough to attempt it myself someday.)

I can't even use PHP 5 anymore on the shared web host I use, DreamHost, ever since Nov. 2019, when they automatically switched all of my websites to PHP 7.

So, the lack of a PHP 5 extension for future versions of Saxon probably wouldn't impact me that much.

But judging by PHP 5's seemingly continuing popularity, I'm guessing it could probably significantly impact other users.

Anyway, I hope this was helpful. Thanks again for all your help, I really appreciate it!

#9 Updated by Christina Spies about 1 month ago

Quoting myself in post 3 - https://saxonica.plan.io/issues/5137?pn=1#note-3 -

I tried the same fix with 1.2,1, but the faulty line in 1.1.2's "php5_saxon.cpp" file appears to have been fixed already in both EE/C 1.2.1 and HE/C 1.2.1. So, I still haven't been able to build those.

I couldn't find a way to edit my original post, so here's the above paragraph reworded to be a bit clearer:

I tried to use the same fix on the newer version, 1.2.1, but was unable to, because in both EE/C 1.2.1 and HE/C 1.2.1, the file "php5_saxon.cpp" no longer had the same problem it used to have in 1.1.2. So, it must be something else which is causing my inability to bulid 1.2.1.


Still, though, this is resolved enough for me for the time being. I'm delighted with Saxon EE/C 1.1.2 as a PHP 5 extension, and Saxon 10.6 for Java. :-)

Thanks again!

#10 Updated by Christina Spies about 1 month ago

Just a few more small corrections that I can't edit into my previous post. Quoting myself in post #7, https://saxonica.plan.io/issues/5137#note-7 :

This more recent page - [[https://w3techs.com/technologies/history_details/pl-php/5]] - titled "Historical trends in the usage statistics of PHP version 5 for websites" - actually says that usage of PHP 5.6 has actually only gone UP from Oct. 2020 to Oct. 2021!

It started at 52.2% in Oct. 2020, and went up to 56.1% by Oct. 2021!

This should have said:

This more recent page - https://w3techs.com/technologies/history_details/pl-php/5 - titled "Historical trends in the usage statistics of PHP version 5 for websites" - shows that usage of PHP 5.6 has actually only gone UP from Oct. 2020 to Oct. 2021!

It started at 52.2% as of Oct. 1, 2020, and went up to 55.9% as of Oct. 1, 2021! (56.1% as of Oct. 21, 2021.)

#11 Updated by Christina Spies about 1 month ago

Oops, I have to make some more corrections already! I just found this other page on the same site, titled "Usage statistics of PHP for websites": https://w3techs.com/technologies/details/pl-php

Quotes:

PHP is used by 78.4% of all the websites whose server-side programming language we know.

[...]

Version 7 68.7% Version 5 29.9%

So, to my relief, PHP 5 on internet-connected web servers actually is a lot less popular than I thought the original page was saying. :-)

This other page - https://w3techs.com/technologies/details/pl-php/5 - says:

Version 5.6 is used by 56.1% of all the websites who use PHP version 5.

Sorry for the confusion!

#12 Updated by O'Neil Delpratt about 1 month ago

Thanks for your comments

Please register to edit this issue

Also available in: Atom PDF