Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <005501c4ba97$2d75cf20$e6ec6f83@robinson.cam.ac.uk> From: "Max Bowsher" To: "Dave Korn" , References: Subject: Re: w32api 3.1 causes mysterious multiple definition errors Date: Mon, 25 Oct 2004 14:33:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned X-IsSubscribed: yes Note-from-DJ: This may be spam Dave Korn wrote: >> -----Original Message----- >> From: cygwin-owner On Behalf Of Max Bowsher >> Sent: 25 October 2004 14:20 > >> w32api is decorating the problem symbols with __declspec(dllimport). >> Fortunately, it is doing so in a #define-controllable manner. >> I will be committing a suitable workaround to setup >> shortly. > > Would the suitable fix be to delete the now-superfluous entries from > autoload.c rather than manipulate the behaviour of the w32api headers with > a > #define? Absolutely NOT. > How does all this interact with 9x, where there aren't any > SID/ACL/Token functions? It would completely break setup on 9x. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/