Josef,

please find out, which of the DLLs/EXEs requires MSVCR80D.dll. This is
fairly simple, just check all dependencies. Currently, we are chasing a
ghost...

Thomas

Stadelmann Josef schrieb:
> Gentlemans very much thank,
> 
> sorry to e not as specific as required, but some of your concerns are almost 
> answered reading my problem;
> 
> 1. I just toke the latest greatest sources from the axis2c trunk and I have 
> REBUILD the axis2c solution
> 
> 2. because there is an IDES directory from which I just clickt 
>       C:\asf\axis\axis2\c\core\trunk\ides\vc9\axis2\axis2c.sln ready to be 
> used with VS2008 
>       (could it be that I got the wrong one here?)
>       (could it be that I better would have opened 
>       C:\asf\axis\axis2\c\core\trunk\ides\vc6\axis2\axis2c.dsw and the 
> convert it to a VS2008 solution?
> 
> 3. As I explained " I want but I can't debug at all the 
> util\test\allocator\allocator_test.c
>       This due to the error box saying that MSVCR80D.dll is not found, 
>       which is in fact the true because it does not exist on  my Vista system;
>       (again, can it be a mismatch because I might have selected the wrong 
> solution file)
> 
> 4. regarding having another binary in the path, my path is quite full, and 
> for sure I have built all from scratch, after a cleanup, so I do not expect 
> that a binary is there which gets engaged when I have build all from scratch. 
> In this case the places reachable by VS2008 are clearly defined.
> 
> 5. I need the MSVCR80D.dll because I want to debug using VS2008; I like to 
> debug the util allocator_test; for that I have built axis2c e all like zlib, 
> libxml2 from scratch. And when that was done error free I was seeking for the 
> project building my axis2c test e all; As there is no such sln file I added 
> just a new consol project to the axis2c solution. (Reason: I have to seek for 
> a nasty bug potentially in libxml2 reader, called by axutil, called by axiom, 
> called by my development project;)  So I created a new project myself and 
> added the existing allocator_test.c; once this was built error free with the 
> axutil.lib and axiom.lib I wanted to debug it, when the error comes up. 
> 
> 6: So to answer, I have built from scratch zlib-1.2.5, libxml2-2.7.7 and 
> axis2c from svn trunk sources, all debug versions, this to dive deep, 
> starting at calling axiom routines then down into axutil, down to 
> libxml2-reader-wrapper into libxml-reader, because only then I can see what 
> goes wrong on my larger server on OpenVMS;
> 
> Why under certain conditions some of my key-tags return a NULL-pointer 
> causing an access violation on entering a axutil-hash-table-entry; 
> 
> So what's wrong?
> Thanks you for your assistance and hope someone has an idea;
> I already placed a call at my help desk to re-install my VS2008 Team Suite 
> inclusing all from VC++ (all libs maybe MSVCR80D.dll is one of it) Web is 
> full of my reported error, but as usual, a lot explain but no true answers.
> 
> 
> Josef
> 
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Thomas Baier [mailto:[email protected]] 
> Gesendet: Donnerstag, 24. Juni 2010 08:18
> An: Apache AXIS C User List
> Betreff: Re: AXIS2C on VISTA / VS9 and DLL Dependencies
> 
> Danushka Menikkumbura schrieb:
>> He has built from source and is not specific if it was debug or release.
> 
> In this case, I would suspect, that the project configuration is wrong.
> VS 2008 should link with MSVCR90D.dll as far as I know. Maybe the import
> library for MSVCR80D.dll has been specified explicitly in the
> makefile/VC project (which normally should not be done)
> 
> Thomas
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to