You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/08/16 12:20:20 UTC
[jira] Closed: (AXISCPP-84) Use of -DUSE_LTDL compilation flag
Message:
The following issue has been closed.
Resolver: Samisa Abeysinghe
Date: Mon, 16 Aug 2004 3:19 AM
Resolved by Damitha.
In the source distribution the USE_LTDL macro is not in Makefiles. If one wants the macro, (s)he could include the macro in the Makefiles.
The following source files use this macro.
src/engine/HandlerLoader.h
src/engine/SOAPTransportFactory.cpp
src/engine/XMLParserFactory.cpp
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-84
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-84
Summary: Use of -DUSE_LTDL compilation flag
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis-C++
Components:
Basic Architecture
Fix Fors:
1.2 Final
Versions:
1.1 Final
Assignee:
Reporter: Adrian Dick
Created: Tue, 4 May 2004 8:30 AM
Updated: Mon, 16 Aug 2004 3:19 AM
Environment: Red Hat 9 (x86) and Red Hat Advanced Server 2.1 (x86)
Description:
I am seeing problems when linking the generated client stubs, relating to a compilation flag in the Axis C++ Client.
On my Red Hat 9 machine, the problem could be resolved by removing -DUSE_LTDL from engine/client/Makefile and rebuilding the Axis C++ Client and generated stubs.
For my Red Hat Advanced Server 2.1 machine, I also needed to make the same modification to engine/server/Makefile.
Based on the comments in the affected piece of code (engine/HanderLoader.cpp), I would not expect the flag -DUSE_LTDL to be specified in the Makefile.
Is this a step missing in the instructions? a problem in the Makefile? or something else?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira