___report_rangecheckfailure unresolved external

[johnmichaloski]

I tried to upgrade the C++ agent code (since agent was hanging/dieing when I stopped the service - very hard to debug) and I downloaded the latest github etc. Compiled ok, but linking - not so good. Libxml xxx.obj had a bunch of buffer overrun unresolved external errors.

I am using MSVC 2010, and the above unresolved external may be from libxml compiling with MSVC 2012. Is there any other recourse besides upgrading to 2012 (or using gnu)?

Is this correct?

[wsobel]

haven’t tested with 2010 – switched to 2012 and thought the libs would be back compatible. you can try to rebuild the libxml libs yourself – i just prebuilt to make it easier since it’s the only depend from the app.

I’m currently building againstv 2.9.1 – available from git://git.gnome.org/libxml2 git://git.gnome.org/libxml2 . It’s all just plain old C, so pretty easy to build. I always build for static linked and multi-threaded: /MT and /MTdls

There is a win32 sudir and if i remember correctly there is a configure.js file you invoke with cscript and then a few selections. I usually choose the minimal features, like no zlib, iconv, ftp, and http, etc… not necessary for MTC. We do need threads though. Make sure you start a windows command prompt for VS 110… If you need help… I can walk you though.

I don’t think I used any new language features that won’t work in 2010. In the future I will be moving off of dlib and onto boost to use their asio and other goodies. this will use more of the c++11 stuff that may not work so well. I put a few bit in the new code base, but nothing major.

On Nov 14, 2014, at 11:45, John Michaloski notifications@github.com wrote:

I tried to upgrade the C++ agent code (since agent was hanging/dieing when I stopped the service - very hard to debug) and I downloaded the latest github etc. Compiled ok, but linking - not so good. Libxml xxx.obj had a bunch of buffer overrun unresolved external errors.

I am using MSVC 2010, and the above unresolved external may be from libxml compiling with MSVC 2012. Is there any other recourse besides upgrading to 2012 (or using gnu)?

Is this correct?

—
Reply to this email directly or view it on GitHub #14.

[johnmichaloski]

Ok, that answered my question. I assumed that, but wanted to make sure before I downloaded and compiled source.

I am using NSIS so I am not tied to msvc 2010 like before. (Next email on nsis on the way).

From: William Sobel [mailto:notifications@github.com]
Sent: Friday, November 14, 2014 3:10 PM
To: mtconnect/cppagent
Cc: Michaloski, John L.
Subject: Re: [cppagent] ___report_rangecheckfailure unresolved external (#14)

haven’t tested with 2010 – switched to 2012 and thought the libs would be back compatible. you can try to rebuild the libxml libs yourself – i just prebuilt to make it easier since it’s the only depend from the app.

I’m currently building againstv 2.9.1 – available from git://git.gnome.org/libxml2 git://git.gnome.org/libxml2 . It’s all just plain old C, so pretty easy to build. I always build for static linked and multi-threaded: /MT and /MTdls

There is a win32 sudir and if i remember correctly there is a configure.js file you invoke with cscript and then a few selections. I usually choose the minimal features, like no zlib, iconv, ftp, and http, etc… not necessary for MTC. We do need threads though. Make sure you start a windows command prompt for VS 110… If you need help… I can walk you though.

I don’t think I used any new language features that won’t work in 2010. In the future I will be moving off of dlib and onto boost to use their asio and other goodies. this will use more of the c++11 stuff that may not work so well. I put a few bit in the new code base, but nothing major.

On Nov 14, 2014, at 11:45, John Michaloski <notifications@github.commailto:notifications@github.com> wrote:

I tried to upgrade the C++ agent code (since agent was hanging/dieing when I stopped the service - very hard to debug) and I downloaded the latest github etc. Compiled ok, but linking - not so good. Libxml xxx.obj had a bunch of buffer overrun unresolved external errors.

I am using MSVC 2010, and the above unresolved external may be from libxml compiling with MSVC 2012. Is there any other recourse besides upgrading to 2012 (or using gnu)?

Is this correct?

—
Reply to this email directly or view it on GitHub #14.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-63122044.