Re: Link errors in apr_atomic with VS2013

2013-11-12 Thread Gregg Smith
On 11/12/2013 10:33 AM, Gregg Smith wrote: On 11/12/2013 10:27 AM, William A. Rowe Jr. wrote: On Fri, 8 Nov 2013 11:00:18 -0800 (PST) Arsen Chaloyan wrote: Anyway, if it turns out the change has to be #ifdef-ed, which is most likely, then testing _MSC_VER only is not enough or appropriate. Pl

Re: Link errors in apr_atomic with VS2013

2013-11-12 Thread William A. Rowe Jr.
On Fri, 8 Nov 2013 11:00:18 -0800 (PST) Arsen Chaloyan wrote: > Anyway, if it turns out the change has to be #ifdef-ed, which is most > likely, then testing _MSC_VER only is not enough or appropriate. > Please note, if one uses VS2013 (_MSC_VER == 1800), it doesn't > necessarily mean that the Pla

Re: Link errors in apr_atomic with VS2013

2013-11-08 Thread Arsen Chaloyan
Agree we should be careful with backward compatibility, but I unfortunately don't have anything below VS2005 to test against. Anyway, if it turns out the change has to be #ifdef-ed, which is most likely, then testing _MSC_VER only is not enough or appropriate. Please note, if one uses VS2013 (_

Re: Link errors in apr_atomic with VS2013

2013-11-08 Thread Gregg Smith
On 11/7/2013 2:10 PM, Arsen Chaloyan wrote: On Thursday, November 7, 2013 4:27 AM, Jeff Trawick wrote: On Thu, Nov 7, 2013 at 12:29 AM, William A. Rowe Jr. mailto:wr...@rowe-clan.net>> wrote: On Tue, 5 Nov 2013 17:49:22 -0800 (PST) Arsen Chaloyan mailto:achalo...@yahoo.com>> wr

Re: Link errors in apr_atomic with VS2013

2013-11-07 Thread Arsen Chaloyan
On Thursday, November 7, 2013 4:27 AM, Jeff Trawick wrote: On Thu, Nov 7, 2013 at 12:29 AM, William A. Rowe Jr. wrote: On Tue, 5 Nov 2013 17:49:22 -0800 (PST) >Arsen Chaloyan wrote: >> >> These errors are caused by the use of the new Platform Toolset v120 >> which gets installed with VS2

Re: Link errors in apr_atomic with VS2013

2013-11-07 Thread Jeff Trawick
On Thu, Nov 7, 2013 at 12:29 AM, William A. Rowe Jr. wrote: > On Tue, 5 Nov 2013 17:49:22 -0800 (PST) > Arsen Chaloyan wrote: > > > > These errors are caused by the use of the new Platform Toolset v120 > > which gets installed with VS2013. More specifically, the problem is > > in the function cas

Re: Link errors in apr_atomic with VS2013

2013-11-06 Thread William A. Rowe Jr.
On Tue, 5 Nov 2013 17:49:22 -0800 (PST) Arsen Chaloyan wrote: > > These errors are caused by the use of the new Platform Toolset v120 > which gets installed with VS2013. More specifically, the problem is > in the function cast wrappers defined in apr_atomic.c and used only > for Win32 (x86) platf

Link errors in apr_atomic with VS2013

2013-11-05 Thread Arsen Chaloyan
Hi, While building the APR library with VS2013 for Win32(x86) platform, the following link errors are encountered. apr_atomic.obj : error LNK2019: unresolved external symbol __InterlockedIncrement referenced in function _apr_atomic_inc32@4 apr_atomic.obj : error LNK2019: unresolved external sym