X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; q=dns; s=default; b= jUZ7ZKIqxR6GD821AACO7Y5zav+mmgeGOeXtkhmlVe0bEFpQu9WoUDaeyNSf8k5b qLFfX67coJEY5pTpJn+LLVUEFz696MG8oU2R+Z+w4YUMLo2ThLp+iIr/fwjufJH/ nkd/5+j+xROWgRQr2nhZp+eoGl1IIAHaMN//PYfVzUw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; s=default; bh=zEqkx YfLfOIX6Jp8Z7wVFkZWf34=; b=E9xm+EAjxXVZymT5Ct8FydwbU/SDgW+WsWLpr +MstDS37zjY2VQ+1WPB72w7xpMJwlr4o9yWzwGPKBiOmtFbE+jqXaqRc2WBL7tGE fBtXCNCIfWWBd+J1111z76xxQNO5RRRb4LQaSlBBYvsohnuxzc0+QZLPUBrL1Tl3 Vt305g= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,NO_RELAYS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f173.google.com MIME-Version: 1.0 X-Received: by 10.50.39.18 with SMTP id l18mr10817038igk.4.1378825137389; Tue, 10 Sep 2013 07:58:57 -0700 (PDT) In-Reply-To: References: <522E4EEE DOT 3010701 AT gmail DOT com> <522F1F7F DOT 5070906 AT gmail DOT com> Date: Tue, 10 Sep 2013 16:58:57 +0200 Message-ID: Subject: Re: Cygwin build errors in mingw-w64 r6257 From: Kai Tietz To: cygwin AT cygwin DOT com Cc: JonY <10walls AT gmail DOT com> Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Well, is there a guard present in cygwin's ntdef.h header? But in general this seems to be a cygwin regression. 2013/9/10 Alexey Pavlov : > Using w2api from mingw-w64 rev.6265 I got the same errors: > > http://pastebin.com/4N8uQ6t1 > > Regards, > Alexey. > > > 2013/9/10 JonY >> >> On 9/10/2013 16:44, Kai Tietz wrote: >> > 2013/9/10 JonY: >> >> Hi, >> >> >> >> Seems like there is a duplicate definition of TRANSACTION_ALL_ACCESS and >> >> THREAD_INFORMATION_CLASS, found by one of the msys2 developers. >> >> >> >> See attached log. >> > >> > I can't see on trunk that those symbols are double defined by >> > mingw-w64. So there might be a different place in cygwin trying to >> > declare them itself. >> > >> > Kai >> > >> >> Alex, >> >> Can you retest with the latest revision? >> >> >> > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple