Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Date: 23 Feb 2004 16:44:16 -0000
Message-ID: <20040223164416.15124.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: axis-dev@ws.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27166] New:  -
    axis c++ doesn't build with gcc 2.96

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27166>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27166

axis c++ doesn't build with gcc 2.96

           Summary: axis c++ doesn't build with gcc 2.96
           Product: Axis-C++
           Version: current (nightly)
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: slang@mcs.anl.gov


The gcc 2.96 compiler appears to be more strict about function pointer
conversion, and will fail to compile the Axis C++ code because there are a
number of function pointers being set in each of the headers IMessageData.h
IWrapperSoapSerializer.h IWrapperSoapDeSerializer.h and Call.h.  I'm submitting
a patch that fixes these problems with a typedef of each function and a cast to
the appropriate type.  

The patch also renames the Call::Initialize_s function, because there are two
functions with the name Initialize_s and you can't pass the first as a function
pointer because it will conflict with the second.  The code that calls
Initialize_s should be updated to reflect that change.