[prev in list] [next in list] [prev in thread] [next in thread] 

List:       aspell-user
Subject:    RE: [Aspell-user] Integrate aspell with PHP
From:       "Pankil Shah" <pankil_shah () persistent ! co ! in>
Date:       2008-05-21 5:55:02
Message-ID: 002901c8bb05$8ac86a80$97194d0a () persistent ! co ! in
[Download RAW message or body]

I think both are similar (as seen in link), but in order to build aspell
using DSO aspell may be needed to be built by apxs tool
(http://httpd.apache.org/docs/1.3/programs/apxs.html)

Also more on DSO can be found at http://httpd.apache.org/docs/1.3/dso.html
It also states that a DSO compatible with Apache needs to symbol from Apache
core. Also such DSO is loaded by mod_so.so instead of ld.so (as in UNIX).

I am not expert in such systems, so please bear with me. This is all I can
help.

Let me know if more clarification is required.

Regards,
Pankil Shah

-----Original Message-----
From: Kevin Atkinson [mailto:kevina@gnu.org] 
Sent: Tuesday, May 20, 2008 10:15 AM
To: Pankil Shah
Cc: aspell-user@gnu.org
Subject: Re: [Aspell-user] Integrate aspell with PHP

On Mon, 19 May 2008, Pankil Shah wrote:

I'm sorry you completely lost me in the second sentence.

> I am on a production system. The machine is RHEL 4 update 3. It has PHP
> (5.8.3) pre-configured with Dynamic Shared Object support enabled.

What exactly is a Dynamic Shared Object and how does it differ from a 
normal shared library?



DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property \
of Persistent Systems Ltd. It is intended only for the use of the individual or \
entity to which it is addressed. If you are not the intended recipient, you are not \
authorized to read, retain, copy, print, distribute or use this message. If you have \
received this communication in error, please notify the sender and delete all copies \
of this message. Persistent Systems Ltd. does not accept any liability for virus \
infected mails.


[prev in list] [next in list] [prev in thread] [next in thread]