Hi ,

As Matt and Martin pointed out there are use cases of the static 
libraries bundled in the default MySQL installation.

My proposal is that we have all the libraries that are given in the 
default MySQL installation. The complete list is as under:

libdbug.a
libmyisam.a
 libmysqlclient_r.a
libmysqlclient_r.so
libmysqlclient.a
 libmysqlclient.so
libmystrings.a
 libmysys.a

plus these two libraries as we are enabling the cluster engine (ndb):

 libndbclient.a
libndbclient.so

We can remove the other static library (ie libheap.a,libvio.a and all 
the .la files as well)

Kindly let me know if that is fine and we shall update the ARC case 
accordingly.

Regards,
Ritu


Matt Ingenthron wrote:

> Danek Duvall wrote:
>
>> On Tue, Oct 23, 2007 at 10:45:23PM -0700, Matt Ingenthron wrote:
>>
>>  
>>
>>> I'd be a bit concerned about this, as I recall PHP mysql modules use 
>>> the static client libraries when it builds by default.  A quick 
>>> search or two seems to confirm this.     
>>
>>
>> It actually puts the full .a file on the link line, rather than using -L
>> and -l?
>>
>> /me shakes his head
>
>
> Agreed...
>
> I'd have to check, but I specifically remember converting the linker 
> args to use the shared object when working on one project.  This could 
> have been left behind in an older version though, or it could have 
> been an artifact of the project I was working on (where PHP had been 
> forked by the customer).
>
> Looking at the under-development Cool Stack, it is dynamically linked:
> # pwd
> /opt/coolstack/php5/lib/php/extensions/no-debug-non-zts-20060613
> # ldd mysql.so
> ...
>         libmysqlclient.so.15 =>  
> /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15
> ...
> # ldd mysqli.so
> ...
>         libmysqlclient.so.15 =>  
> /opt/coolstack/mysql_32bit/lib/mysql/libmysqlclient.so.15
> ...
>
> The end of this posting is interesting: 
> http://bugs.php.net/bug.php?id=34516 -- if it's correct, they didn't 
> include shared libraries by default in MySQL circa January 2006.
>
>
> - Matt
>


Reply via email to