[ 
https://issues.apache.org/jira/browse/AXIS2C-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Mengué updated AXIS2C-1437:
-----------------------------------

    Attachment: inst-libs.sh

Workaround: copy the .so.0 manually as .so. I wrote the following (also 
attached) script to do that:

#!/usr/bin/sh

[[ -z "$deploy_dir" ]] && exit 2

cd ${1:-axis2c-src-1.6.0}

cp $(find . -name '*.so.0') $deploy_dir/lib
cd $deploy_dir/lib
for f in *.so.0
do
        x=$(basename $f .0)
        [[ -h $x ]] || ln -s -f $f $x
done
mv libaxis2_mod_addr.* ../modules/addressing
mv libaxis2_mod_log.* ../modules/logging


> AIX: dynamic libraries are built but not installed
> --------------------------------------------------
>
>                 Key: AXIS2C-1437
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1437
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: build system (Unix/Linux)
>    Affects Versions: 1.6.0, 1.7.0, Current (Nightly)
>         Environment: AIX 5.3
>            Reporter: Olivier Mengué
>         Attachments: inst-libs.sh
>
>
> On AIX, the dynamic are correctly built, but they are not installed by "make 
> install". I only have .a and .la in $deploy_dir/lib. No .so.
> It looks like that the dynamic libraries are build with a ".so.0" extension 
> instead of just ".so"
> # find . -name '*.so'
> # find . -name '*.so*'
> ./guththila/src/.libs/libguththila.so.0
> ./util/src/.libs/libaxutil.so.0
> ./neethi/src/.libs/libneethi.so.0
> ./axiom/src/xpath/.libs/libaxis2_xpath.so.0
> ./axiom/src/om/.libs/libaxis2_axiom.so.0
> ./axiom/src/parser/guththila/.libs/libaxis2_parser.so.0
> ./src/modules/mod_log/.libs/libaxis2_mod_log.so.0
> ./src/modules/mod_addr/.libs/libaxis2_mod_addr.so.0
> ./src/core/transport/http/sender/.libs/libaxis2_http_sender.so.0
> ./src/core/transport/http/receiver/.libs/libaxis2_http_receiver.so.0
> ./src/core/transport/http/common/.libs/libaxis2_http_common.so.0
> ./src/core/engine/.libs/libaxis2_engine.so.0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to