From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14726 invoked by alias); 26 Nov 2012 00:02:48 -0000 Received: (qmail 14718 invoked by uid 22791); 26 Nov 2012 00:02:47 -0000 X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from muon.cran.org.uk (HELO muon.cran.org.uk) (93.89.92.64) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Nov 2012 00:02:42 +0000 Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 35BDAE65EA for ; Mon, 26 Nov 2012 00:07:07 +0000 (GMT) Received: from [IPv6:2a01:348:301:2:2827:2d9e:7939:abfb] (unknown [IPv6:2a01:348:301:2:2827:2d9e:7939:abfb]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 0CAD7E65E5 for ; Mon, 26 Nov 2012 00:07:07 +0000 (GMT) Message-ID: <50B2B1A1.30906@cran.org.uk> Date: Mon, 26 Nov 2012 00:02:00 -0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: pthreads-win32@sourceware.org Subject: Re: pthreadVC2.dll dependency on MSVCR100.dll References: <50AFDB38.8000109@cran.org.uk> <50B2A513.5030409@homemail.com.au> In-Reply-To: <50B2A513.5030409@homemail.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2012/txt/msg00032.txt.bz2 On 25/11/2012 23:09, Ross Johnson wrote: > Not deliberate. I assume this is a default and one reference I found > claims it is linked to by msvcrt.lib in VS 2010. I'm looking but I > haven't found a solution yet that I like (assuming it's correct the > same reference suggests either linking statically or building with an > old environment - both unacceptable ). If both those are unacceptable then the only solution will be to document the dependency. The last toolset which allowed linking to msvcrt.dll was WDK 7.1, and that has now been superseded by WDK 8.0, which uses VS 2012 instead of an ancient set of compilers. I confirmed with Doron at Microsoft earlier this year that it's now a requirement to link against VS's CRT (http://www.osronline.com/showthread.cfm?link=221792). Why is statically linking the CRT unacceptable? -- Bruce Cran