maria-developers team mailing list archive

["Vladislav Vaintroub" <wlad@xxxxxxxxxxxxxxxx>]

Steve, 
Are you talking about PIC requirements, when you say " HP-UX doesn't support
building shared libaries that depend on archive libraries".  

In MySQL 5.5, linking static to shared  feature was used extensively (as a
replacement for libtool's "convenience libraries", static library was
compiled with platform dependent PIC flag), and it worked on all major
Unixes, I'm pretty sure it worked on  HPUX/Itanium.

I think the trick for Maria 5.3 could be to compile the sqlservices library
with the PIC flag (+Z or +z or something similar, if I recall this
correctly). I do not have access to HPUX machines anymore, but you might
want to give it a try.


> -----Original Message-----
> From: maria-developers-
> bounces+wlad=montyprogram.com@xxxxxxxxxxxxxxxxxxx [mailto:maria-
> developers-bounces+wlad=montyprogram.com@xxxxxxxxxxxxxxxxxxx] On
> Behalf Of Steve Ellcey
> Sent: Donnerstag, 22. September 2011 23:12
> To: maria-developers@xxxxxxxxxxxxxxxxxxx
> Subject: [Maria-developers] Shared plugin library build question
> 
> I am looking at a difference in the HP-UX vs. Linux mariadb build and
> was wondering if someone could help me understand why something is set
> up the way it is.
> 
> The problem I see is that on HP-UX, when I do a mariadb build I do not
> get shared plugin libraries like ha_federated.  Looking into why this
> was happening I found that when the plugin libraries like ha_federated
> are built they have a dependency on libsqlservices and libsqlservices
> is built only as an archive library.  HP-UX doesn't support building
> shared libaries that depend on archive libraries and so the build of the
> shared plugin libraries fails when no shared version of libsqlservices
> is found.
> 
> So my main question is: why is libsqlservices built only as an archive
> library?  The other question is: if libsqlservices has to be an archive
> only library, is there is another way to link it in to executables, such
> as linking it in explicitly when building an executable instead of
> counting on the shared plugin libraries to bring it in indirectly by
> making it a dependent library?
> 
> Steve Ellcey
> sje@xxxxxxxxxx
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-developers
> Post to     : maria-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp