X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4AB2F018.2060803@users.sourceforge.net> Date: Thu, 17 Sep 2009 21:27:36 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: libtool: possible candidate for attribute 'noreturn' Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Chuck, Compiling libcanberra-0.17 (which adds tons of -W flags) with latest libtool and gcc-4.3.2-2: CCLD test-canberra.exe ./.libs/lt-test-canberra.c: In function 'lt_fatal': ./.libs/lt-test-canberra.c:582: warning: function might be possible candidate for attribute 'noreturn' [-Wmissing-noreturn] Perhaps someone can explain why only this function, and not others which "return" void, trigger this warning. In any case, while I still don't understand why libtool insists on compiling lt-*.c with the same flags as the actual code itself, I'll leave this to you to determine if and how this should be fixed. Yaakov -- 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