O'Neil Delpratt
- Login: ond1
- Email: oneil@saxonica.com
- Registered on: 2012-01-26
- Last connection: 2023-01-25
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 38 | 557 | 595 |
Reported issues | 27 | 349 | 376 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter | 2012-01-27 |
Saxon-CE | Developer, Reporter | 2012-02-01 |
SaxonC | Manager, Developer, Reporter | 2013-11-28 |
SaxonJS | Manager, Developer, Reporter | 2016-08-11 |
SaxonMirrorHE | Manager, Developer | 2021-02-02 |
Activity
2023-01-26
-
-
Please can you detail the error message for description how it fails. Bug #5858: Python Saxonche module doesn't work using Pyinstaller and UPX processing to create executable fileI'm using Pyinstaller with UPX processing to create executable files from Python scripts. I was using a Python module Saxonpy and decided to move away from this module to use instead Saxonche. The issue I have now by using this module is...
-
This error actually seems related to the following bug issue: https://saxonica.plan.io/issues/5856
```
I want to add that I had to install libc6 because it needed GLIBC_2.32 instead of the default version provided by Debian. You can ... Saxon/C Help and Discussions: RE: Building commands on Debian 11 fails: /usr/bin/ld: /home/mh/libsaxon-HEC-linux-v12.0/command/../libs/nix/libsaxon-hec-12.0.so: undefined reference to `pthread_attr_getguardsize@GLIBC_2.34'
I am currently trying to use SaxonC 12.0 HE on WSL Debian 11, I get various ld errors when trying to build e.g. the commands:
```
mh@LibertyDell:~/libsaxon-HEC-linux-v12.0/command$ ./build-saxonc-commands.sh
/usr/bin/ld: /home/mh/... -
Do the C+ samples work? -
I have also reproduced the same error on linux. Something strange going on here. I will create a bug issue for this problem. Saxon/C Help and Discussions: RE: Problems to use self built Python extension on Windows: ImportError: DLL load failed while importing saxonche
I have tried to build the SaxonC 12.0 HE extension on Windows and I think the extension finally has been built fine.
Now on trying to use it, however, it doesn't seem to find a library:
```
C:\Program Files\Saxonica\SaxonCHE12.0... -
Thank you for reporting this issue. I have applied the fix to the method name and also added the `setRelocatable`, `setFastCompilation`, `setXsltCompilation` and `setFastCompilation` to the set of available methods for the `Xslt30Process... Bug #5856 (Resolved): Compilation/build issue PHP 8Hi all, I'm very excited to see a new SaxonC version for PHP 8! I wanted immediately to give it a try, but ran into a small issue.
I used Docker to prepare a full build file for you guys to reproduce the issue (and maybe to give other...
2023-01-25
-
You should be able to reproduce the error by following the C++ samples instructions here: https://www.saxonica.com/saxon-c/documentation12/index.html#!starting/running
I did the following to reproduce the error:
```
sudo cp libs/d... Bug #4617: macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.I tried to run the sample C++ program with Saxon/C on macOS Catalina 10.15.4. Getting the following error:
~~~
macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.
~~~
There is an u... -
Bug issue created here: #5854 Saxon/C Help and Discussions: RE: Should PyDocumentBuilder have exception_occurred/error_message properties to report parse errors?I am wondering how to handle errors occurring during XML parsing with PyDocumentBuilder in my code, it seems the document builder itself has no properties like exception_occurred or error_message, those on the PySaxonProcessor don't seem...
-
-
The nodekind.py file dependency has been removed. This should not make any difference to the Python API. Bug #5853 (Resolved): ModuleNotFundError: No module named 'nodeKind'Reported by user on Windows machine the following error when running a simple python script:
```
import saxonche
File "python_saxon\saxonc.pyx", line 16, in init saxonche
ModuleNotFundError: No module named 'nodeKind'
```
I ...
Also available in: Atom