From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mx1.pokylinux.org (Postfix) with ESMTP id D867C4C810C1 for ; Wed, 12 Jan 2011 05:38:35 -0600 (CST) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p0CBeGf1026113; Wed, 12 Jan 2011 11:40:17 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Hb6A+idqMb2N; Wed, 12 Jan 2011 11:40:16 +0000 (GMT) Received: from [192.168.1.42] (tim [93.97.173.237]) (authenticated bits=0) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p0CBe9gF026107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Jan 2011 11:40:11 GMT From: Richard Purdie To: "Garman, Scott A" In-Reply-To: <4D2CA815.6060205@intel.com> References: <4D2CA815.6060205@intel.com> Date: Wed, 12 Jan 2011 11:38:13 +0000 Message-ID: <1294832293.15313.2018.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Cc: Yocto Project Discussion Subject: Re: Libtoo sysrootl issue when testing machine specific sysroot X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 11:38:36 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2011-01-11 at 10:57 -0800, Garman, Scott A wrote: > On 01/10/2011 07:15 PM, Xu, Dongxiao wrote: > > Hi Richard, > > > > When testing the machine specific sysroot patchset for atom-pc and > > emenlow machines, it exposed a libtool issue that, after the built of > > "Machine A", and then try to build "Machine B" of the same > > architecture, those "-L" paths generated by libtool still points to > > the "Machine A" sysroot, which is definitely not correct and may have > > issues. > > Thanks Donxiao for the info. I will make sure to test this scenario > before submitting my libtool 2.4 sysroot support to ensure it is resolved. I talked a little with Dongxiao about this and it looks like he needs to improve the functionality in sstate to cope with sysroot per machine. This isn't to say that the libtool 2.4 sysroot support won't reduce the amount of relocation work those functions need to do which is all good but both changes are needed independently of each other. Cheers, Richard