From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by mx1.pokylinux.org (Postfix) with ESMTP id 16E284C80050 for ; Tue, 22 Mar 2011 11:41:01 -0500 (CDT) Authentication-Results: mx1.pokylinux.org; dkim=pass (1024-bit key; insecure key) header.i=madison@cisco.com; x-dkim-adsp=none (insecure policy) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=madison@cisco.com; l=2327; q=dns/txt; s=iport; t=1300812061; x=1302021661; h=date:subject:from:to:message-id:mime-version; bh=7NkXxeuEPdS34aGXKPIVuRCxhEDsr/6vp/VP2COAlgk=; b=BLWtdCV21zG6sW6a2annvN2UoQC9vqqNeIZwN+/AcYWPuAz5/Dp5WEbK mPEkgiLlKL2nP5OElPKjaalmGU9RyAFBuTsJpFkhpoLKPIt8l+ltS6Nf2 E7/LtG+vhdCdsDih1pWgkK2QyTRgsrMg3mUBTnOa/nVFarqQ26d4I8JCB w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApUFAPttiE2rRDoG/2dsb2JhbACCYaF/VAJ3pnCcTIVoBIU1hzaDWIVJ X-IronPort-AV: E=Sophos;i="4.63,225,1299456000"; d="scan'208,217";a="280929890" Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 22 Mar 2011 16:41:00 +0000 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2MGf0us018535 for ; Tue, 22 Mar 2011 16:41:00 GMT Received: from xmb-sjc-217.amer.cisco.com ([171.70.151.175]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Mar 2011 09:41:00 -0700 Received: from 128.107.159.176 ([128.107.159.176]) by xmb-sjc-217.amer.cisco.com ([171.70.151.175]) with Microsoft Exchange Server HTTP-DAV ; Tue, 22 Mar 2011 16:40:59 +0000 User-Agent: Microsoft-Entourage/12.28.0.101117 Date: Tue, 22 Mar 2011 09:40:53 -0700 From: Matt Madison To: Yocto Mailer Message-ID: Thread-Topic: Older versions of Linux as build hosts? Thread-Index: Acvor+ih8u5ArlEO6EmxWZmoHMnn0w== Mime-version: 1.0 X-OriginalArrivalTime: 22 Mar 2011 16:41:00.0509 (UTC) FILETIME=[ED1B20D0:01CBE8AF] Subject: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 16:41:01 -0000 Content-type: multipart/alternative; boundary="B_3383631655_56443806" --B_3383631655_56443806 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Hi, I know the documentation mentions that you should be running a =B3reasonably current=B2 Linux as your build host, but in my enterprise environment I=B9m stuck with having to run fairly old versions, based on RHEL 4 and 5. I=B9ve got some patches that I=B9ve been maintaining so I can bootstrap Bernard builds on these systems. Is there any interest in supporting older systems as build hosts? Any thoughts on how far back =B3reasonably current=B2 is going to be with each Yocto release? I=B9m trying to work with my IT group to upgrade a bit more frequently, and for developer workstations, that might b= e possible, but I=B9m not sure I=B9ll be able to convince them to do that for servers in our data centers. Is anyone else having this kind of problem? Thanks, -Matt --B_3383631655_56443806 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Older versions of Linux as build hosts? Hi,

I know the documentation mentions that you should be running a “reaso= nably current” Linux as your build host, but in my enterprise environm= ent I’m stuck with having to run fairly old versions, based on RHEL 4 = and 5.  I’ve got some patches that I’ve been maintaining so= I can bootstrap Bernard builds on these systems.  Is there any interes= t in supporting older systems as build hosts?  Any thoughts on how far = back “reasonably current” is going to be with each Yocto release= ?  I’m trying to work with my IT group to upgrade a bit more freq= uently, and for developer workstations, that might be possible, but I’= m not sure I’ll be able to convince them to do that for servers in our= data centers.

Is anyone else having this kind of problem?

Thanks,
-Matt --B_3383631655_56443806-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mx1.pokylinux.org (Postfix) with ESMTP id 352524C800BA for ; Tue, 22 Mar 2011 11:48:19 -0500 (CDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p2MGmIIf003539 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Mar 2011 09:48:18 -0700 (PDT) Received: from Macintosh-5.local (172.25.36.233) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.1.255.0; Tue, 22 Mar 2011 09:48:17 -0700 Message-ID: <4D88D2D0.7050202@windriver.com> Date: Tue, 22 Mar 2011 11:48:16 -0500 From: Mark Hatle Organization: Wind River Systems User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Matt Madison References: In-Reply-To: X-Originating-IP: [172.25.36.233] Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 16:48:19 -0000 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit On 3/22/11 11:40 AM, Matt Madison wrote: > Hi, > I have done builds with both RHEL 4 and RHEL 5. Both on machines in which I do not have root access. For me I was able to simply provide an update python, some additional tools and it worked. (Note, I haven't tried it in the last 2 months though, so something may have broken since then.) > I know the documentation mentions that you should be running a “reasonably > current” Linux as your build host, but in my enterprise environment I’m stuck > with having to run fairly old versions, based on RHEL 4 and 5. I’ve got some > patches that I’ve been maintaining so I can bootstrap Bernard builds on these > systems. Is there any interest in supporting older systems as build hosts? Any > thoughts on how far back “reasonably current” is going to be with each Yocto > release? I’m trying to work with my IT group to upgrade a bit more frequently, > and for developer workstations, that might be possible, but I’m not sure I’ll be > able to convince them to do that for servers in our data centers. > > Is anyone else having this kind of problem? I think this is a fairly typical problem. In my experience it's usually easier to solve in a commercial space then pure open source. As for the question about interest, we're always interested in patches. At a minimum, it would be nice to document what steps you had to do and what patches you may have had to apply in order to get "unsupported" functionality out of the build environment. The yocto wiki seems a fairly natural place for this. So please send what you have, or start an account on the Yocto Wiki and post it there. --Mark > Thanks, > -Matt > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.pokylinux.org (Postfix) with ESMTP id 16FA84C800BB for ; Tue, 22 Mar 2011 12:00:42 -0500 (CDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 22 Mar 2011 10:00:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.63,225,1299484800"; d="scan'208";a="900044561" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by fmsmga001.fm.intel.com with ESMTP; 22 Mar 2011 10:00:18 -0700 Received: from orsmsx601.amr.corp.intel.com (10.22.226.213) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 22 Mar 2011 10:00:17 -0700 Received: from orsmsx504.amr.corp.intel.com ([10.22.226.207]) by orsmsx601.amr.corp.intel.com ([10.22.226.213]) with mapi; Tue, 22 Mar 2011 10:00:17 -0700 From: "Rifenbark, Scott M" To: Mark Hatle , Matt Madison Date: Tue, 22 Mar 2011 10:00:13 -0700 Thread-Topic: [yocto] Older versions of Linux as build hosts? Thread-Index: AcvosPeBWjAn0ceaTYWqBoK/lj6xagAAWnEQ Message-ID: References: <4D88D2D0.7050202@windriver.com> In-Reply-To: <4D88D2D0.7050202@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 17:00:42 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes - the wiki is a great place for this type of information. All the spec= ifics for a particular build system and the steps you have to take to make = it work can be collected there. Then from the Quick Start we can mention w= here to get support information for older versions. ScottR -----Original Message----- From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org= ] On Behalf Of Mark Hatle Sent: Tuesday, March 22, 2011 9:48 AM To: Matt Madison Cc: Yocto Mailer Subject: Re: [yocto] Older versions of Linux as build hosts? On 3/22/11 11:40 AM, Matt Madison wrote: > Hi, >=20 I have done builds with both RHEL 4 and RHEL 5. Both on machines in which = I do not have root access. For me I was able to simply provide an update python, some additional tools= and it worked. (Note, I haven't tried it in the last 2 months though, so somet= hing may have broken since then.) > I know the documentation mentions that you should be running a "reasonabl= y > current" Linux as your build host, but in my enterprise environment I'm s= tuck > with having to run fairly old versions, based on RHEL 4 and 5. I've got = some > patches that I've been maintaining so I can bootstrap Bernard builds on t= hese > systems. Is there any interest in supporting older systems as build host= s? Any > thoughts on how far back "reasonably current" is going to be with each Yo= cto > release? I'm trying to work with my IT group to upgrade a bit more frequ= ently, > and for developer workstations, that might be possible, but I'm not sure = I'll be > able to convince them to do that for servers in our data centers. >=20 > Is anyone else having this kind of problem? I think this is a fairly typical problem. In my experience it's usually ea= sier to solve in a commercial space then pure open source. As for the question about interest, we're always interested in patches. At= a minimum, it would be nice to document what steps you had to do and what pat= ches you may have had to apply in order to get "unsupported" functionality out o= f the build environment. The yocto wiki seems a fairly natural place for this. So please send what you have, or start an account on the Yocto Wiki and pos= t it there. --Mark > Thanks, > -Matt >=20 >=20 >=20 > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yx0-f176.google.com (mail-yx0-f176.google.com [209.85.213.176]) by mx1.pokylinux.org (Postfix) with ESMTP id DD5BB4C802F2 for ; Tue, 22 Mar 2011 12:01:48 -0500 (CDT) Authentication-Results: mx1.pokylinux.org; dkim=pass (1024-bit key; insecure key) header.i=@gmail.com; x-dkim-adsp=none (insecure policy) Received: by yxd5 with SMTP id 5so3877301yxd.35 for ; Tue, 22 Mar 2011 10:01:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=15iBpBYq0YjGThIh+55wfFjl2q4jaXlS4cNg6ZYnoKA=; b=g7AmhABLq1M4dwub9ky0G2FV/jMbg/47HOh1epVPDf34kBGPet7lVa4IBsvLJREApA W1oK8Ds+821Pe4R5iys/br9a5POXJk+/TMEbCpyQRqUTbjyozFfz4EYHvgU7YtDxqN85 /FDFPAGJuOLHCHVLd0Vl0FcTqF2FIw91HU1hc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=e1JApycPSkRgivLw9knH7RGWbJ0+iuj0Is1+owL3ukavxJRBPGAZ8EDVAC1mje7Gcz ud09nMNgfsn1dLPkLCuU1HfACIP0pjmfLCBQtxyH5aNykDgZlxLZVcIvZPyw6OfGxi4W ezNtCnQretdkr+p61cXQWDbA+D6BCnS1NNVSY= Received: by 10.151.145.18 with SMTP id x18mr64571ybn.133.1300813308359; Tue, 22 Mar 2011 10:01:48 -0700 (PDT) Received: from [10.0.10.113] (gateway-1237.mvista.com [206.112.117.35]) by mx.google.com with ESMTPS id t12sm3702024ybe.0.2011.03.22.10.01.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Mar 2011 10:01:47 -0700 (PDT) Message-ID: <4D88D5F6.4020306@gmail.com> Date: Tue, 22 Mar 2011 10:01:42 -0700 From: Jeremy Puhlman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Mark Hatle References: <4D88D2D0.7050202@windriver.com> In-Reply-To: <4D88D2D0.7050202@windriver.com> Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 17:01:49 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 3/22/2011 9:48 AM, Mark Hatle wrote: > On 3/22/11 11:40 AM, Matt Madison wrote: >> Hi, >> > I have done builds with both RHEL 4 and RHEL 5. Both on machines in which I do > not have root access. > > For me I was able to simply provide an update python, some additional tools and > it worked. (Note, I haven't tried it in the last 2 months though, so something > may have broken since then.) I have noticed of late, pseudo's definition of clone conflicts with my RHEL 4's definition of clone. Aside from that I haven't noticed any significant issues. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by mx1.pokylinux.org (Postfix) with ESMTP id 3A5454C808B6 for ; Tue, 22 Mar 2011 12:02:53 -0500 (CDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 22 Mar 2011 10:02:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.63,225,1299484800"; d="scan'208";a="406565064" Received: from unknown (HELO [10.255.16.45]) ([10.255.16.45]) by azsmga001.ch.intel.com with ESMTP; 22 Mar 2011 10:02:39 -0700 From: Joshua Lock To: yocto@yoctoproject.org In-Reply-To: References: Date: Tue, 22 Mar 2011 16:51:02 +0000 Message-ID: <1300812662.2793.21.camel@scimitar> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 17:02:53 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Tue, 2011-03-22 at 09:40 -0700, Matt Madison wrote: > Hi, > > I know the documentation mentions that you should be running a > “reasonably current” Linux as your build host, but in my enterprise > environment I’m stuck with having to run fairly old versions, based on > RHEL 4 and 5. I’ve got some patches that I’ve been maintaining so I > can bootstrap Bernard builds on these systems. Is there any interest > in supporting older systems as build hosts? Any thoughts on how far > back “reasonably current” is going to be with each Yocto release? I’m > trying to work with my IT group to upgrade a bit more frequently, and > for developer workstations, that might be possible, but I’m not sure > I’ll be able to convince them to do that for servers in our data > centers. > > Is anyone else having this kind of problem? We have other users suffering with this sort of problem which is why Richard worked to enable Poky to build an external Python tarball. This tarball should include what you need (Python + chrpath) to run Poky on RHEL: http://autobuilder.yoctoproject.org/downloads/miscsupport/ I documented this for CentOS on the Yocto wiki: https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies Regards, Joshua -- Joshua Lock Yocto Build System Monkey Intel Open Source Technology Centre From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by mx1.pokylinux.org (Postfix) with ESMTP id 5DF0C4C80050 for ; Tue, 22 Mar 2011 12:10:17 -0500 (CDT) Authentication-Results: mx1.pokylinux.org; dkim=pass (1024-bit key; insecure key) header.i=madison@cisco.com; x-dkim-adsp=none (insecure policy) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=madison@cisco.com; l=2883; q=dns/txt; s=iport; t=1300813817; x=1302023417; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=mj+cZjNcGDvbdRC7ZNDokPL4qV9qSW8x0wlSqJ0pF5I=; b=KU8gF6aJmNBhT1pGHsc8E6nGJNvoDgBc1o2b5cGgX5cLwtgCofRhIrL/ exth4wtrvt1MWtZXFJ6hUeLAGyO006lWwAxj4k6TFeQ+FsxeUz6ClCQR7 iRCnLdVur5AK75tiisGcOf51DSCCMlEQWcFOLEEjJ456+AW07SGwpacv4 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0AAFB0iE2rRDoH/2dsb2JhbACYAY00AneITZ4gnEODDoJaBIU1hhiBHoNYhUk X-IronPort-AV: E=Sophos;i="4.63,225,1299456000"; d="scan'208";a="416905842" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-1.cisco.com with ESMTP; 22 Mar 2011 17:10:16 +0000 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2MHAGGV015704; Tue, 22 Mar 2011 17:10:16 GMT Received: from xmb-sjc-217.amer.cisco.com ([171.70.151.175]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Mar 2011 10:10:16 -0700 Received: from 128.107.159.176 ([128.107.159.176]) by xmb-sjc-217.amer.cisco.com ([171.70.151.175]) with Microsoft Exchange Server HTTP-DAV ; Tue, 22 Mar 2011 17:10:15 +0000 User-Agent: Microsoft-Entourage/12.28.0.101117 Date: Tue, 22 Mar 2011 10:10:07 -0700 From: Matt Madison To: "Rifenbark, Scott M" , Mark Hatle Message-ID: Thread-Topic: [yocto] Older versions of Linux as build hosts? Thread-Index: AcvosPeBWjAn0ceaTYWqBoK/lj6xagAAWnEQAABnNPo= In-Reply-To: Mime-version: 1.0 X-OriginalArrivalTime: 22 Mar 2011 17:10:16.0544 (UTC) FILETIME=[03C8CE00:01CBE8B4] Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 17:10:17 -0000 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit OK, sounds good. I'll go through my notes and transcribe them to the wiki. -Matt On 3/22/11 10:00 , "Rifenbark, Scott M" wrote: > Yes - the wiki is a great place for this type of information. All the > specifics for a particular build system and the steps you have to take to make > it work can be collected there. Then from the Quick Start we can mention > where to get support information for older versions. > > ScottR > > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] > On Behalf Of Mark Hatle > Sent: Tuesday, March 22, 2011 9:48 AM > To: Matt Madison > Cc: Yocto Mailer > Subject: Re: [yocto] Older versions of Linux as build hosts? > > On 3/22/11 11:40 AM, Matt Madison wrote: >> Hi, >> > > I have done builds with both RHEL 4 and RHEL 5. Both on machines in which I > do > not have root access. > > For me I was able to simply provide an update python, some additional tools > and > it worked. (Note, I haven't tried it in the last 2 months though, so > something > may have broken since then.) > >> I know the documentation mentions that you should be running a "reasonably >> current" Linux as your build host, but in my enterprise environment I'm stuck >> with having to run fairly old versions, based on RHEL 4 and 5. I've got some >> patches that I've been maintaining so I can bootstrap Bernard builds on these >> systems. Is there any interest in supporting older systems as build hosts? >> Any >> thoughts on how far back "reasonably current" is going to be with each Yocto >> release? I'm trying to work with my IT group to upgrade a bit more >> frequently, >> and for developer workstations, that might be possible, but I'm not sure I'll >> be >> able to convince them to do that for servers in our data centers. >> >> Is anyone else having this kind of problem? > > I think this is a fairly typical problem. In my experience it's usually > easier > to solve in a commercial space then pure open source. > > As for the question about interest, we're always interested in patches. At a > minimum, it would be nice to document what steps you had to do and what > patches > you may have had to apply in order to get "unsupported" functionality out of > the > build environment. The yocto wiki seems a fairly natural place for this. > > So please send what you have, or start an account on the Yocto Wiki and post > it > there. > > --Mark > >> Thanks, >> -Matt >> >> >> >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mx1.pokylinux.org (Postfix) with ESMTP id EB0094C802F2 for ; Tue, 22 Mar 2011 18:24:54 -0500 (CDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p2MNOrVq010515 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Mar 2011 16:24:53 -0700 (PDT) Received: from Macintosh-5.local (172.25.36.233) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.1.255.0; Tue, 22 Mar 2011 16:24:53 -0700 Message-ID: <4D892FC3.1010306@windriver.com> Date: Tue, 22 Mar 2011 18:24:51 -0500 From: Mark Hatle Organization: Wind River Systems User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jeremy Puhlman References: <4D88D2D0.7050202@windriver.com> <4D88D5F6.4020306@gmail.com> In-Reply-To: <4D88D5F6.4020306@gmail.com> X-Originating-IP: [172.25.36.233] Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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: Tue, 22 Mar 2011 23:24:55 -0000 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit On 3/22/11 12:01 PM, Jeremy Puhlman wrote: > On 3/22/2011 9:48 AM, Mark Hatle wrote: >> On 3/22/11 11:40 AM, Matt Madison wrote: >>> Hi, >>> >> I have done builds with both RHEL 4 and RHEL 5. Both on machines in which I do >> not have root access. >> >> For me I was able to simply provide an update python, some additional tools and >> it worked. (Note, I haven't tried it in the last 2 months though, so something >> may have broken since then.) > > I have noticed of late, pseudo's definition of clone conflicts with my > RHEL 4's definition of clone. Aside > from that I haven't noticed any significant issues. semantics of clone changed between RHEL 4 and RHEL 5. :( The newer version of pseudo (upstream, not yet in Poky) fixes this issue. It's still in development, so I wouldn't consider it stable yet -- but the reworking of the utility directories is what was needed to identify the differences. --Mark From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tim.rpsys.net (93-97-173-237.zone5.bethere.co.uk [93.97.173.237]) by mx1.pokylinux.org (Postfix) with ESMTP id 653AB4C800BA for ; Wed, 23 Mar 2011 12:49:07 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p2NHn1dJ004288; Wed, 23 Mar 2011 17:49:01 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 02947-10; Wed, 23 Mar 2011 17:48:57 +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 p2NHmrV4004279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Mar 2011 17:48:54 GMT From: Richard Purdie To: Mark Hatle In-Reply-To: <4D892FC3.1010306@windriver.com> References: <4D88D2D0.7050202@windriver.com> <4D88D5F6.4020306@gmail.com> <4D892FC3.1010306@windriver.com> Date: Wed, 23 Mar 2011 17:48:51 +0000 Message-ID: <1300902531.3018.41.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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, 23 Mar 2011 17:49:07 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2011-03-22 at 18:24 -0500, Mark Hatle wrote: > On 3/22/11 12:01 PM, Jeremy Puhlman wrote: > > On 3/22/2011 9:48 AM, Mark Hatle wrote: > >> On 3/22/11 11:40 AM, Matt Madison wrote: > >>> Hi, > >>> > >> I have done builds with both RHEL 4 and RHEL 5. Both on machines in which I do > >> not have root access. > >> > >> For me I was able to simply provide an update python, some additional tools and > >> it worked. (Note, I haven't tried it in the last 2 months though, so something > >> may have broken since then.) > > > > I have noticed of late, pseudo's definition of clone conflicts with my > > RHEL 4's definition of clone. Aside > > from that I haven't noticed any significant issues. > > semantics of clone changed between RHEL 4 and RHEL 5. :( > > The newer version of pseudo (upstream, not yet in Poky) fixes this issue. > > It's still in development, so I wouldn't consider it stable yet -- but the > reworking of the utility directories is what was needed to identify the differences. For what its worth, poky master is now moving ahead with new changes so if you do have updates for master, the tree is open for them. Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by mx1.pokylinux.org (Postfix) with ESMTP id 998A24C80479 for ; Wed, 23 Mar 2011 14:36:55 -0500 (CDT) Authentication-Results: mx1.pokylinux.org; dkim=pass (1024-bit key; insecure key) header.i=madison@cisco.com; x-dkim-adsp=none (insecure policy) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=madison@cisco.com; l=7584; q=dns/txt; s=iport; t=1300909015; x=1302118615; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=i9wNsFtJ55LvoHC3OwbN2C/diagDdkgZoe8nEXUUv9U=; b=TvtkathNAudlZYUGcvmIMEj87JcqpQRflm7i/uifwGKRqcq/K3z5X/7v Ynqbam+sINVE4bwD9pkCbln9NXKLSozY5x90PVrqSNjhV7Kd0LEPkrTzk Mij7BoERMWrh7VkE75xvmZjWQHR0DAVHSZkQ69JLycgOXsqPC321o1kKO Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: At8AAPfoiU2rRDoG/2dsb2JhbACCYJUsjGBZd4hNnjecLIMPgloEhTeGGYEfg1g X-IronPort-AV: E=Sophos;i="4.63,233,1299456000"; d="scan'208,217";a="417468429" Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 23 Mar 2011 19:36:54 +0000 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2NJasNB017953; Wed, 23 Mar 2011 19:36:54 GMT Received: from xmb-sjc-217.amer.cisco.com ([171.70.151.175]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 23 Mar 2011 12:36:54 -0700 Received: from 10.21.114.61 ([10.21.114.61]) by xmb-sjc-217.amer.cisco.com ([171.70.151.175]) via Exchange Front-End Server email.cisco.com ([171.70.151.187]) with Microsoft Exchange Server HTTP-DAV ; Wed, 23 Mar 2011 19:36:53 +0000 User-Agent: Microsoft-Entourage/12.28.0.101117 Date: Wed, 23 Mar 2011 12:36:51 -0700 From: Matt Madison To: "Rifenbark, Scott M" , Mark Hatle Message-ID: Thread-Topic: [yocto] Older versions of Linux as build hosts? Thread-Index: AcvosPeBWjAn0ceaTYWqBoK/lj6xagAAWnEQADfRtSk= In-Reply-To: Mime-version: 1.0 X-OriginalArrivalTime: 23 Mar 2011 19:36:54.0466 (UTC) FILETIME=[AA2AEA20:01CBE991] Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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, 23 Mar 2011 19:36:56 -0000 Content-type: multipart/alternative; boundary="B_3383728611_1768571" --B_3383728611_1768571 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable I=B9ve posted some notes at https://wiki.yoctoproject.org/wiki/BuildingOnRHEL= 4 and will update further as I find more things to work around. -Matt On 3/22/11 10:00 AM, "Rifenbark, Scott M" wrote: > Yes - the wiki is a great place for this type of information. All the > specifics for a particular build system and the steps you have to take to= make > it work can be collected there. Then from the Quick Start we can mention > where to get support information for older versions. >=20 > ScottR >=20 > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.o= rg] > On Behalf Of Mark Hatle > Sent: Tuesday, March 22, 2011 9:48 AM > To: Matt Madison > Cc: Yocto Mailer > Subject: Re: [yocto] Older versions of Linux as build hosts? >=20 > On 3/22/11 11:40 AM, Matt Madison wrote: >> > Hi, >> > >=20 > I have done builds with both RHEL 4 and RHEL 5. Both on machines in whic= h I > do > not have root access. >=20 > For me I was able to simply provide an update python, some additional too= ls > and > it worked. (Note, I haven't tried it in the last 2 months though, so > something > may have broken since then.) >=20 >> > I know the documentation mentions that you should be running a "reason= ably >> > current" Linux as your build host, but in my enterprise environment I'= m >> stuck >> > with having to run fairly old versions, based on RHEL 4 and 5. I've g= ot >> some >> > patches that I've been maintaining so I can bootstrap Bernard builds o= n >> these >> > systems. Is there any interest in supporting older systems as build h= osts? >> Any >> > thoughts on how far back "reasonably current" is going to be with each >> Yocto >> > release? I'm trying to work with my IT group to upgrade a bit more >> frequently, >> > and for developer workstations, that might be possible, but I'm not su= re >> I'll be >> > able to convince them to do that for servers in our data centers. >> > >> > Is anyone else having this kind of problem? >=20 > I think this is a fairly typical problem. In my experience it's usually > easier > to solve in a commercial space then pure open source. >=20 > As for the question about interest, we're always interested in patches. = At a > minimum, it would be nice to document what steps you had to do and what > patches > you may have had to apply in order to get "unsupported" functionality out= of > the > build environment. The yocto wiki seems a fairly natural place for this. >=20 > So please send what you have, or start an account on the Yocto Wiki and p= ost > it > there. >=20 > --Mark >=20 >> > Thanks, >> > -Matt >> > >> > >> > >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >=20 > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >=20 --B_3383728611_1768571 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [yocto] Older versions of Linux as build hosts? I’ve posted some notes at https://wiki.yoctoproject.org/wiki/BuildingOnRHEL4 an= d will update further as I find more things to work around.

-Matt


On 3/22/11 10:00 AM, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com> wrote:

<= SPAN STYLE=3D'font-size:10pt'>Yes - the wiki is a great place for this type of= information.  All the specifics for a particular build system and the = steps you have to take to make it work can be collected there.  Then fr= om the Quick Start we can mention where to get support information for older= versions.

ScottR

-----Original Message-----
From: yocto-bounces@yoctoproject.o= rg [mailto:yocto-bounces= @yoctoproject.org] On Behalf Of Mark Hatle
Sent: Tuesday, March 22, 2011 9:48 AM
To: Matt Madison
Cc: Yocto Mailer
Subject: Re: [yocto] Older versions of Linux as build hosts?

On 3/22/11 11:40 AM, Matt Madison wrote:
> Hi,
>

I have done builds with both RHEL 4 and RHEL 5.  Both on machines in w= hich I do
not have root access.

For me I was able to simply provide an update python, some additional tools= and
it worked.  (Note, I haven't tried it in the last 2 months though, so = something
may have broken since then.)

> I know the documentation mentions that you should be running a "r= easonably
> current" Linux as your build host, but in my enterprise environme= nt I'm stuck
> with having to run fairly old versions, based on RHEL 4 and 5.  I= 've got some
> patches that I've been maintaining so I can bootstrap Bernard builds o= n these
> systems.  Is there any interest in supporting older systems as bu= ild hosts?  Any
> thoughts on how far back "reasonably current" is going to be= with each Yocto
> release?  I'm trying to work with my IT group to upgrade a bit mo= re frequently,
> and for developer workstations, that might be possible, but I'm not su= re I'll be
> able to convince them to do that for servers in our data centers.
>
> Is anyone else having this kind of problem?

I think this is a fairly typical problem.  In my experience it's usual= ly easier
to solve in a commercial space then pure open source.

As for the question about interest, we're always interested in patches. &nb= sp;At a
minimum, it would be nice to document what steps you had to do and what pat= ches
you may have had to apply in order to get "unsupported" functiona= lity out of the
build environment.  The yocto wiki seems a fairly natural place for th= is.

So please send what you have, or start an account on the Yocto Wiki and pos= t it
there.

--Mark

> Thanks,
> -Matt
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.= yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yocto= project.org/listinfo/yocto

--B_3383728611_1768571-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by mx1.pokylinux.org (Postfix) with ESMTP id 8F0B84C804D9 for ; Wed, 23 Mar 2011 14:39:23 -0500 (CDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 23 Mar 2011 12:39:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.63,233,1299484800"; d="scan'208,217";a="407410552" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by azsmga001.ch.intel.com with ESMTP; 23 Mar 2011 12:39:20 -0700 Received: from orsmsx606.amr.corp.intel.com (10.22.226.128) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 23 Mar 2011 12:39:06 -0700 Received: from orsmsx504.amr.corp.intel.com ([10.22.226.207]) by orsmsx606.amr.corp.intel.com ([10.22.226.128]) with mapi; Wed, 23 Mar 2011 12:39:06 -0700 From: "Rifenbark, Scott M" To: Matt Madison , Mark Hatle Date: Wed, 23 Mar 2011 12:39:04 -0700 Thread-Topic: [yocto] Older versions of Linux as build hosts? Thread-Index: AcvosPeBWjAn0ceaTYWqBoK/lj6xagAAWnEQADfRtSkAAAqrUA== Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Yocto Mailer Subject: Re: Older versions of Linux as build hosts? 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, 23 Mar 2011 19:39:24 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DE8BA75F34A0404282AC5E15F691BC7650A6EABForsmsx504amrcor_" --_000_DE8BA75F34A0404282AC5E15F691BC7650A6EABForsmsx504amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Matt, Thanks for putting that information on the wiki. I will add a note to the = QS that points there for information on older systems. ScottR From: Matt Madison [mailto:madison@cisco.com] Sent: Wednesday, March 23, 2011 12:37 PM To: Rifenbark, Scott M; Mark Hatle Cc: Yocto Mailer Subject: Re: [yocto] Older versions of Linux as build hosts? I've posted some notes at https://wiki.yoctoproject.org/wiki/BuildingOnRHEL= 4 and will update further as I find more things to work around. -Matt On 3/22/11 10:00 AM, "Rifenbark, Scott M" wro= te: Yes - the wiki is a great place for this type of information. All the spec= ifics for a particular build system and the steps you have to take to make = it work can be collected there. Then from the Quick Start we can mention w= here to get support information for older versions. ScottR -----Original Message----- From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org= ] On Behalf Of Mark Hatle Sent: Tuesday, March 22, 2011 9:48 AM To: Matt Madison Cc: Yocto Mailer Subject: Re: [yocto] Older versions of Linux as build hosts? On 3/22/11 11:40 AM, Matt Madison wrote: > Hi, > I have done builds with both RHEL 4 and RHEL 5. Both on machines in which = I do not have root access. For me I was able to simply provide an update python, some additional tools= and it worked. (Note, I haven't tried it in the last 2 months though, so somet= hing may have broken since then.) > I know the documentation mentions that you should be running a "reasonabl= y > current" Linux as your build host, but in my enterprise environment I'm s= tuck > with having to run fairly old versions, based on RHEL 4 and 5. I've got = some > patches that I've been maintaining so I can bootstrap Bernard builds on t= hese > systems. Is there any interest in supporting older systems as build host= s? Any > thoughts on how far back "reasonably current" is going to be with each Yo= cto > release? I'm trying to work with my IT group to upgrade a bit more frequ= ently, > and for developer workstations, that might be possible, but I'm not sure = I'll be > able to convince them to do that for servers in our data centers. > > Is anyone else having this kind of problem? I think this is a fairly typical problem. In my experience it's usually ea= sier to solve in a commercial space then pure open source. As for the question about interest, we're always interested in patches. At= a minimum, it would be nice to document what steps you had to do and what pat= ches you may have had to apply in order to get "unsupported" functionality out o= f the build environment. The yocto wiki seems a fairly natural place for this. So please send what you have, or start an account on the Yocto Wiki and pos= t it there. --Mark > Thanks, > -Matt > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto --_000_DE8BA75F34A0404282AC5E15F691BC7650A6EABForsmsx504amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Re: [yocto] Older versions of Linux as build hosts?

Matt,

 

Thanks for putting that information on the wiki.  I wil= l add a note to the QS that points there for information on older systems.

 

ScottR

 

From: Matt Madison [mailto:madison@cisco.com]
Sent: Wednesday, March 23, 2011 12:37 PM
To: Rifenbark, Scott M; Mark Hatle
Cc: Yocto Mailer
Subject: Re: [yocto] Older versions of Linux as build hosts?

 

I’ve posted some notes at https://wiki.yo= ctoproject.org/wiki/BuildingOnRHEL4 and will update further as I find more things to work around.

-Matt


On 3/22/11 10:00 AM, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com> wr= ote:

Yes - the wiki is a great place for thi= s type of information.  All the specifics for a particular build system = and the steps you have to take to make it work can be collected there.  Th= en from the Quick Start we can mention where to get support information for ol= der versions.

ScottR

-----Original Message-----
From: yocto-bounces@yoctoproject= .org [mailto:yocto-bounces@yoc= toproject.org] On Behalf Of Mark Hatle
Sent: Tuesday, March 22, 2011 9:48 AM
To: Matt Madison
Cc: Yocto Mailer
Subject: Re: [yocto] Older versions of Linux as build hosts?

On 3/22/11 11:40 AM, Matt Madison wrote:
> Hi,
>

I have done builds with both RHEL 4 and RHEL 5.  Both on machines in w= hich I do
not have root access.

For me I was able to simply provide an update python, some additional tools= and
it worked.  (Note, I haven't tried it in the last 2 months though, so something
may have broken since then.)

> I know the documentation mentions that you should be running a "reasonably
> current" Linux as your build host, but in my enterprise environme= nt I'm stuck
> with having to run fairly old versions, based on RHEL 4 and 5.  I= 've got some
> patches that I've been maintaining so I can bootstrap Bernard builds o= n these
> systems.  Is there any interest in supporting older systems as bu= ild hosts?  Any
> thoughts on how far back "reasonably current" is going to be with each Yocto
> release?  I'm trying to work with my IT group to upgrade a bit mo= re frequently,
> and for developer workstations, that might be possible, but I'm not su= re I'll be
> able to convince them to do that for servers in our data centers.
>
> Is anyone else having this kind of problem?

I think this is a fairly typical problem.  In my experience it's usual= ly easier
to solve in a commercial space then pure open source.

As for the question about interest, we're always interested in patches.  At a
minimum, it would be nice to document what steps you had to do and what pat= ches
you may have had to apply in order to get "unsupported" functiona= lity out of the
build environment.  The yocto wiki seems a fairly natural place for th= is.

So please send what you have, or start an account on the Yocto Wiki and pos= t it
there.

--Mark

> Thanks,
> -Matt
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://list= s.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoc= toproject.org/listinfo/yocto

--_000_DE8BA75F34A0404282AC5E15F691BC7650A6EABForsmsx504amrcor_--