From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1S8Xxx-0005qw-Oy for openembedded-core@lists.openembedded.org; Fri, 16 Mar 2012 15:17:14 +0100 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q2GE82Pr003825; Fri, 16 Mar 2012 14:08:02 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02357-08; Fri, 16 Mar 2012 14:07:58 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q2GE7t6D003819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Mar 2012 14:07:56 GMT Message-ID: <1331906876.18586.186.camel@ted> From: Richard Purdie To: openembedded-core Date: Fri, 16 Mar 2012 14:07:56 +0000 X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: "Eggleton, Paul" , "sanil.kumar" Subject: Fixing Warnings X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 14:17:14 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit We need to ensure we don't overlap with the warning message fixing work. I've created: https://wiki.yoctoproject.org/wiki/Warning_Fixing which has a list of the remaining warnings I know about and has an indication of who (if anyone) is addressing them. Please check there before working on any given warning message. The good news is we're down to about 115 of them for world assuming the pending patches merge. I'm tempted to turn off the exec_prefix cross linkage warnings in the release branch for this release since the fixes for those could be too invasive to take the risk on at this point in the release cycle and most users probably don't need to see those warnings. Those warnings should be treated as the lowest priority. Cheers, Richard