Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 9632 invoked from network); 15 Oct 2007 06:57:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Oct 2007 06:57:43 -0000 Received: (qmail 41173 invoked by uid 500); 15 Oct 2007 06:57:31 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 41005 invoked by uid 500); 15 Oct 2007 06:57:30 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 40994 invoked by uid 99); 15 Oct 2007 06:57:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Oct 2007 23:57:30 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2007 06:57:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AFA4871422C for ; Sun, 14 Oct 2007 23:56:50 -0700 (PDT) Message-ID: <12113607.1192431410716.JavaMail.jira@brutus> Date: Sun, 14 Oct 2007 23:56:50 -0700 (PDT) From: "Nandika Jayawardana (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Resolved: (AXIS2C-722) The subject of C Run-Time depending on compilation option /MT, /MD In-Reply-To: <10353561.1192151750812.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXIS2C-722?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandika Jayawardana resolved AXIS2C-722. ---------------------------------------- Resolution: Fixed I changed the build options in makefile and allowed the user to specify the= CRUNTIME library in configure.in file. When building axis2c , it will be b= uild with /MD option by default. Also when building Axis2 with VC2005 or ab= ove, it generates the .manifest file which has the runtime library informat= ion. > The subject of C Run-Time depending on compilation option /MT, /MD=20 > ------------------------------------------------------------------- > > Key: AXIS2C-722 > URL: https://issues.apache.org/jira/browse/AXIS2C-722 > Project: Axis2-C > Issue Type: Improvement > Components: build system (Windows) > Affects Versions: Current (Nightly) > Environment: OS: WindowsXP > Compiler : MSVC > Reporter: Atsushi Monna > > I think Axis2/C has a problem about C Run-Time in windows. > I made a dll calling Axis2/C public function using file stream in axutil. > When I used this dll, access violation was occured. > In concretely,=20 > I use the axutil_stream_t object created by axutil_stream_create_file(con= st axutil_env_t *env, FILE *fp) in axutil_stream_read(). I caught a access = violation. > Reason is ... > The file pointer above can not use in this DLL(axutil.dll), because Axis2= /C builded with /MT option. > The relation between MSVC compliation option and C Run-Time Libraries is = indicated in this page. > http://msdn2.microsoft.com/en-us/library/abx4dbyh(VS.80).aspx > The problem depending on C Run-Time Libraries is indicated in this page. > http://msdn2.microsoft.com/en-us/library/ms235460(VS.80).aspx > Every Axis2/C module has static C Run-Time in local. So, boundaries exist= among all. > =20 > To be valid the public function has file pointer argument in axutil, use = /MD compilation option for common C Run-Time (not exist boundaries) amonng = all. > But this way is not enough. If the C Run-Time version depended Axis2/C mo= dules are defferent with the C Run-Time version depended module that callin= g Axis2/C modules API, same problem will occur. > I think, complete solution for this problem is Axis2/C binary release bui= lded with /MD compilation option and specify C Run-Time Library version.=20 > I hope above. > Depending C Run-Time version depend on build environment. For any user us= ing Axis2/C binary release, provide some binary release for every C Run-Tim= e versions. It is better I think. > If I cann't get Axis2/C binary release like this, I hope the lowest that = Axis2/C be clear the policy in a document for this problem. > =E3=83=BBAxis2/C binary release builded using /MT compilation option. > =E3=83=BBThis modules has some problem depending C Run-Time Libraries. > =E3=83=BBIf you call Axis2/C module's API, you need to re-build Axis2/C u= sing /MD compilation option. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org