From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.pokylinux.org (Postfix) with ESMTP id 949674C800A9 for ; Tue, 12 Jul 2011 08:19:33 -0500 (CDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 12 Jul 2011 06:19:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,521,1304319600"; d="scan'208";a="24890535" Received: from unknown (HELO helios.localnet) ([10.255.17.183]) by orsmga002.jf.intel.com with ESMTP; 12 Jul 2011 06:19:22 -0700 From: Paul Eggleton To: poky@yoctoproject.org Date: Tue, 12 Jul 2011 14:19:21 +0100 User-Agent: KMail/1.13.6 (Linux/2.6.38-8-generic-pae; KDE/4.6.2; i686; ; ) References: <4E1C32B3.8090708@mlbassoc.com> <4E1C429E.7010506@mlbassoc.com> <201107121412.20663.paul.eggleton@linux.intel.com> In-Reply-To: <201107121412.20663.paul.eggleton@linux.intel.com> MIME-Version: 1.0 Message-Id: <201107121419.21197.paul.eggleton@linux.intel.com> Subject: Re: BusyBox features not working X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 13:19:33 -0000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Tuesday 12 July 2011 14:12:20 Paul Eggleton wrote: > On Tuesday 12 July 2011 13:48:30 Gary Thomas wrote: > > Weird. I just ran through this, first with the default value for > > DISTRO_FEATURES, then with the same value but 'ipv4' placed at the front > > of that list. If 'ipv4' is somewhere in the middle, busybox is not > > configured correctly. If it's at the front, it works properly. > > Hmm, a quick test shows that you're right, it doesn't seem to be working as > expected. Not sure what's going on yet but I will investigate further. OK, so the answer is it's not fully expanding DISTRO_FEATURES in busybox.inc, thus nothing in DISTRO_FEATURES_LIBC is found. I'll send a patch to fix this (to oe-core). Thanks for pointing this out! Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre