"Joseph, Anselm" <anselm.jos...@fpl.com> writes:

> Hello all,
> Any chance someone has some time to take a look at the attached files
> and give me some pointers. I am not making any progress at all.
> Thanks in advance.

This page:

https://www.ibm.com/developerworks/aix/library/au-gnu.html

tells me that AIX has two sorts of shared libraries: native shared
libraries in .a files and SysV compatible shared libraries in .so files.

When Subversion attempts to install mod_dav_svn it delegates to Apache's
apxs, e.g. on my Linux system:

$ make -n install-mods-shared
if true ; then cd subversion/mod_dav_svn ; /usr/bin/install -c -d 
"/usr/local/subversion/apache" ; /usr/bin/apxs2 -i -S 
LIBEXECDIR="/usr/local/subversion/apache"  -n dav_svn mod_dav_svn.la ; fi
if true ; then cd subversion/mod_authz_svn ; /usr/bin/install -c -d 
"/usr/local/subversion/apache" ; /usr/bin/apxs2 -i -S 
LIBEXECDIR="/usr/local/subversion/apache"  -n authz_svn mod_authz_svn.la ; fi

Looking at your error:

libtool: install: cp .libs/mod_dav_svn.aT
/opt/eai/ci/subversion-1.9.5/svn/libexec/mod_dav_svn.a
libtool: install: cp .libs/mod_dav_svn.lai
/opt/eai/ci/subversion-1.9.5/svn/libexec/mod_dav_svn.la
chmod 755 /opt/eai/ci/subversion-1.9.5/svn/libexec/mod_dav_svn.so
chmod: /opt/eai/ci/subversion-1.9.5/svn/libexec/mod_dav_svn.so: A file
or directory in the path name does not exist.
apxs:Error: Command failed with rc=65536

mod_dav_svn.a (a AIX native shared library) is being copied but the
chmod expects mod_dav_svn.so (a SysV compatible shared library).

It looks like Apache's apxs doesn't properly handle AIX native shared
libraries.

I don't know what the correct solution is on AIX.  I don't know whether
Apache on AIX expects to load .a or .so modules, or whether it can
handle both.  Are your other Apache modules .so or .a?

Perhaps there is a compiler or linker option that will get the linker to
produce SysV .so libraries instead of AIX .a libraries?

Perhaps you could modify apxs to avoid doing the chmod?

As a hack you could create dummy .so files in the installation directory
so that the chmod succeeds.

-- 
Philip

Reply via email to