From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-vk0-x22e.google.com ([2607:f8b0:400c:c05::22e]) by metis.ext.pengutronix.de with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bUskW-000331-RE for ptxdist@pengutronix.de; Wed, 03 Aug 2016 11:46:05 +0200 Received: by mail-vk0-x22e.google.com with SMTP id n129so141538310vke.3 for ; Wed, 03 Aug 2016 02:46:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160803080437.GG11824@pengutronix.de> References: <20160803080437.GG11824@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Wed, 3 Aug 2016 11:45:57 +0200 Message-ID: Subject: Re: [ptxdist] Patched glibc in a ptxdist BSP List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============1091837135==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============1091837135== Content-Type: multipart/alternative; boundary=001a114783b245ad30053927b30b --001a114783b245ad30053927b30b Content-Type: text/plain; charset=UTF-8 Hi Michael, 2016-08-03 10:04 GMT+02:00 Michael Olbrich : > Hi, > > On Tue, Aug 02, 2016 at 07:06:55PM +0200, Guillermo Rodriguez Garcia wrote: > > I need to include a patched version of glibc in a ptxdist BSP. I know > that > > glibc itself is not compiled as part of the BSP, but as part of the > > toolchain. What is the best way to generate a patched glibc without > > recompiling the toolchain ? Is there a recommended procedure for this? > > There is no procedure for this. The libc is part of toolchain, and mixing > different versions is not a good idea. > And at least with an OSELAS.Toolchain, rebuilding it isn't really a > problem. It's just a PTXdist project. > Thank you for your answer. Probably I did not explain my problem correctly. Rebuilding the toolchain per se is not a problem; the problem is how to deploy the patched library. The process of rebuilding the toolchain basically installs the (fixed) toolchain in my development machine. This is perfect for the regular development cycle, however in this case what I really need is a way to deploy a hotfix with the patched library on the target systems (that are already running). So I was looking for a way to generate an ipkg/opkg or something that I can easily deploy. Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a114783b245ad30053927b30b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Michael,

2016-08-03 10:04 GMT+02:00 Michael Olbrich <m.olbr= ich@pengutronix.de>:
Hi,
On Tue, Aug 02, 2016 at 07:06:55PM +0200, Guillermo Rodriguez Garcia wrote:=
> I need to include a patched version of glibc in a ptxdist BSP. I know = that
> glibc itself is not compiled as part of the BSP, but as part of the > toolchain. What is the best way to generate a patched glibc without > recompiling the toolchain ? Is there a recommended procedure for this?=

There is no procedure for this. The libc is part of toolchain, and m= ixing
different versions is not a good idea.
And at least with an OSELAS.Toolchain, rebuilding it isn't really a
problem. It's just a PTXdist project.

Thank you for your answer. Probably I did not explain my problem correct= ly. Rebuilding the toolchain per se is not a problem; the problem is how to= deploy the patched library. The process of rebuilding the toolchain basica= lly installs the (fixed) toolchain in my development machine. This is perfe= ct for the regular development cycle, however in this case what I really ne= ed is a way to deploy a hotfix with the patched library on the target syste= ms (that are already running). So I was looking for a way to generate an ip= kg/opkg or something that I can easily deploy.

Guillermo R= odriguez Garcia
guille.rodriguez@gmail.com
--001a114783b245ad30053927b30b-- --===============1091837135== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1091837135==--