Saxon » SaxonC

Hi,

Is it possible for you to try setting the environment variable SAXONC_HOME=/usr/lib64 or to where you have installed the libsaxoneec.so library.

Hi,

Just did, and the previous error is gone. However now I have other errors.

It was the quickest support I ever received :)

Thanks a lot.

Kind Regards

Muhammad Mostafizur Rahman

Senior Software Engineer

London, UK

+44(0)7782153151

On 26 January 2017 at 16:46, Saxonica Developer Community <

notifications@plan.io> wrote:

Thank you, I should create another ticket but its related to the same setup.

When running ldconfig it says,

/sbin/ldconfig.real: file /usr/lib/libsaxoneec.so is truncated

The conversion still went correctly. But should we be worried as it will be used commercially?

Muhammad Rahman wrote:

Thank you, I should create another ticket but its related to the same setup.

When running ldconfig it says,

/sbin/ldconfig.real: file /usr/lib/libsaxoneec.so is truncated

The conversion still went correctly. But should we be worried as it will be used commercially?

No you should not be worried. The library was created using the professional tool: Excelsior Jet

Thanks O'Nell

Our company(affiliate window) uses php7 but your library is in php5.5.

What do you suggest in that case. We can always write our own wrapper around the C library and execute in command line from php.

But that would be better if you can tell us your plan/solution about using it with php 7.

Thanks.

Hi,

At the moment we are working towards a new major version of Saxon/C which we hope to support PHP7. We never like to give firm dates on releases, but I think it should be in this first quarter of the 2017.

Have you tried building the current Saxon/C against PHP6?

Hi,

Did you mean php 5.6? I am not aware of PHP6, I thought it never existed.

As your timeline seems later than our deadline, it seems we need to execute the c command line from our php 7 library, which is yet to write.

Hi,

Another thought. If we use your php5.5 library for now, how difficult will it be to upgrade to your php7 library? Will you be using the same interface? or we have to recode a lot?

Thanks.

Have you tried building Saxon/C yourself against PHP7?

Another user tried it. See the bug issue: https://saxonica.plan.io/issues/3084

The bug is still open as some of the errors have not been resolved. But you might be able to resolve them.

We have since been working hard on the next major release for Saxon/C with a redesign of how we interface with PHP. This will in turn support PHP7 and older releases. Therefore we are reluctant to go backwards and patch Saxon/C version 1.0 at this stage to support PHP7 since it was not designed for that version of PHP.

Maybe we can suggest sending you a pre-release of the next Saxon/C product for testing purposes.

Hi O'Nell

We had a little chat and possibly the direction for us is using your C command line tool from our php 7 library.

We will absolutely love to test the pre-release php 7 version of yours. After lunch I am going to build my docker with php 7 and see what issue it raises.

Please do send us the pre-release version. If you need my company email, that will be muhammad.rahman@affiliatewindow.com. Send to whichever you may please.

Thanks.

Hi O'Nell,

We are looking into executing the java and C commnad from php 7 now and bench-marking for the best option. So far java looks good. Transforming 800mb took around 1.32 mins. By the way, I never managed to transfer a 7 gig xml, always memory/times runs out. What would the best practice for that using your tool.

If you can send your pre-release version, that will be best time for us to bench mark that too.

Regards.

Muhammad.

For comparison I've been running transformations on 100Mb (on the Java platform) where my timings are roughly:

Stylesheet compilation - 350ms

Tree building - 1400ms

Stylesheet execution - 100ms

but of course it depends what the stylesheet is actually doing.

To transform 7Gb you'll definitely need to look at XSLT 3.0 streaming transformations - which can be quite easy to write in simple cases, but quite difficult in more complex cases.

Hi MIchael,

Thanks for your prompt reply. I am trying to play around wit streaming, but unfortunately it doesn't recognise the element. Keep saying

unknown xslt element stream

Here is what I am trying, my xml

<?xml version="1.0" encoding="UTF-8"?>

<transactions>

  <transaction value="12.51"/>

  <transaction value="3.99"/>

</transactions>

My xsl

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0">

<xsl:template match="/">

<xsl:mode streamable="yes" />

    <xsl:stream href="transactions.xml">

      <count>

        <xsl:value-of select="count(transactions/transaction)"/>

      </count>

    </xsl:stream>

</xsl:template>

</xsl:stylesheet>

And the command I am trying,

java -Xmx4096m -cp ~/Downloads/saxon9ee.jar net.sf.saxon.Transform -t -s:transactions.xml -xsl:transactions.xsl

Hope you can find the error.

Also any news about your php 7 pre-release branch for us to test?

Thanks.

Saxon/C pre-release still not ready. I will try to send it to you tomorrow.

Hi O'Nell,

Thanks. We probably will go for running c compiler from php as we found it faster that java. But we need the steaming running, as a huge number of xmls are several gigs.

Thanks for your time, please have a look at the above snippets.

Talk to you soon.

You mention c compiler. Is that with Saxon/C or some thing else?

In regards to your error message in comment #15 it probably means you are running Saxon without a valid license or in HE mode. Please can you confirm what product you are running. XSLT Streaming requires the Saxon EE edition with a valid license file.

Ah, it make sense now.

OK, I will try with the evaluation license.

Yes, we are using the Saxon/C compiler from php 7.

Ok great.

Is it possible that you can create new bug entries for issues other than the initial issue raised please. Otherwise it will be difficult to keep track and close the bug entry when fixed.

Thanks