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==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ua0-x232.google.com ([2607:f8b0:400c:c08::232]) by metis.ext.pengutronix.de with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bUd9i-0004lp-UT for ptxdist@pengutronix.de; Tue, 02 Aug 2016 19:07:03 +0200 Received: by mail-ua0-x232.google.com with SMTP id 35so133941582uap.1 for ; Tue, 02 Aug 2016 10:07:02 -0700 (PDT) MIME-Version: 1.0 From: Guillermo Rodriguez Garcia Date: Tue, 2 Aug 2016 19:06:55 +0200 Message-ID: Subject: [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="===============0292251733==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============0292251733== Content-Type: multipart/alternative; boundary=94eb2c0d06767831b3053919be5e --94eb2c0d06767831b3053919be5e Content-Type: text/plain; charset=UTF-8 Hello all, 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? Thank you, Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --94eb2c0d06767831b3053919be5e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

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 rec= ommended procedure for this?

Thank you= ,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
--94eb2c0d06767831b3053919be5e-- --===============0292251733== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0292251733==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <201608031448.29494.jbe@pengutronix.de> References: <201608031206.46603.jbe@pengutronix.de> <201608031448.29494.jbe@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Wed, 3 Aug 2016 15:46:34 +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="===============0800397269==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: Juergen Borleis Cc: "ptxdist@pengutronix.de" --===============0800397269== Content-Type: multipart/alternative; boundary=001a113d3bd4c9796a05392b0f36 --001a113d3bd4c9796a05392b0f36 Content-Type: text/plain; charset=UTF-8 Hi Juergen, 2016-08-03 14:48 GMT+02:00 Juergen Borleis : > Hi, > > On Wednesday 03 August 2016 13:29:07 Guillermo Rodriguez Garcia wrote: > > [...] > > > > 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. > > > > > > There should be a "platform-/packages/glibc_2.16.0_*.ipk" which > > > could do this job. > > > > Perfect, this is (almost) what I need. Thank you. > > > > I think ptxdist installs ipkg utils on the host by default, but I cannot > > find them. Perhaps it is a private copy? > > ? > > $ l platform-/sysroot-host/bin/opkg > -rwxr-xr-x 2 jbe ptx 38824 Jul 19 15:34 > platform-/sysroot-host/bin/opkg > > HOST_PACKAGE_MANAGEMENT_OPKG=y (and thus HOST_OPKG=y and HOST_OPKG_UTILS=y > -> but I'm using ptxdist master) > > And this IPK-package ("platform-/packages/glibc_2.16.0_*.ipk") is > generated by the regular rule "rules/glibc.make" for every PTXdist project. > Great. Thank you for your help! Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a113d3bd4c9796a05392b0f36 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Juergen,

2016-08-03 14:48 GMT+02:00 Juergen Borleis <jbe@pengutro= nix.de>:
Hi,

On Wednesday 03 August 2016 13:29:07 Guillermo Rodriguez Garcia wrote:
> [...]
> > > Rebuilding the toolchain per se is not a pr= oblem; the problem is how to
> > > deploy the patched library. The process of rebuilding the to= olchain
> > > basically installs the (fixed) toolchain in my development m= achine.
> > > This is perfect for the regular development cycle, however i= n this case
> > > what I really need is a way to deploy a hotfix with the patc= hed library
> > > on the target systems (that are already running). So I was l= ooking for a
> > > way to generate an ipkg/opkg or something that I can easily = deploy.
> >
> > There should be a "platform-<name>/packages/glibc_2.16= .0_*.ipk" which
> > could do this job.
>
> Perfect, this is (almost) what I need. Thank you.
>
> I think ptxdist installs ipkg utils on the host by default, but I cann= ot
> find them. Perhaps it is a private copy?

?

$ l platform-<name>/sysroot-host/bin/opkg
-rwxr-xr-x 2 jbe ptx 38824 Jul 19 15:34 platform-<name>/sysroot-host/= bin/opkg

HOST_PACKAGE_MANAGEMENT_OPKG=3Dy (and thus HOST_OPKG=3Dy and HOST_OPKG_UTIL= S=3Dy
-> but I'm using ptxdist master)

And this IPK-package ("platform-<name>/packages/glibc_2.16.0_*.i= pk") is
generated by the regular rule "rules/glibc.make" for every PTXdis= t project.

Great. Thank you for your he= lp!

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.c= om
--001a113d3bd4c9796a05392b0f36-- --===============0800397269== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0800397269==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Borleis Date: Wed, 3 Aug 2016 14:48:29 +0200 References: <201608031206.46603.jbe@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201608031448.29494.jbe@pengutronix.de> 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de Cc: Guillermo Rodriguez Garcia SGksCgpPbiBXZWRuZXNkYXkgMDMgQXVndXN0IDIwMTYgMTM6Mjk6MDcgR3VpbGxlcm1vIFJvZHJp Z3VleiBHYXJjaWEgd3JvdGU6Cj4gWy4uLl0KPiA+ID4gUmVidWlsZGluZyB0aGUgdG9vbGNoYWlu IHBlciBzZSBpcyBub3QgYSBwcm9ibGVtOyB0aGUgcHJvYmxlbSBpcyBob3cgdG8KPiA+ID4gZGVw bG95IHRoZSBwYXRjaGVkIGxpYnJhcnkuIFRoZSBwcm9jZXNzIG9mIHJlYnVpbGRpbmcgdGhlIHRv b2xjaGFpbgo+ID4gPiBiYXNpY2FsbHkgaW5zdGFsbHMgdGhlIChmaXhlZCkgdG9vbGNoYWluIGlu IG15IGRldmVsb3BtZW50IG1hY2hpbmUuCj4gPiA+IFRoaXMgaXMgcGVyZmVjdCBmb3IgdGhlIHJl Z3VsYXIgZGV2ZWxvcG1lbnQgY3ljbGUsIGhvd2V2ZXIgaW4gdGhpcyBjYXNlCj4gPiA+IHdoYXQg SSByZWFsbHkgbmVlZCBpcyBhIHdheSB0byBkZXBsb3kgYSBob3RmaXggd2l0aCB0aGUgcGF0Y2hl ZCBsaWJyYXJ5Cj4gPiA+IG9uIHRoZSB0YXJnZXQgc3lzdGVtcyAodGhhdCBhcmUgYWxyZWFkeSBy dW5uaW5nKS4gU28gSSB3YXMgbG9va2luZyBmb3IgYQo+ID4gPiB3YXkgdG8gZ2VuZXJhdGUgYW4g aXBrZy9vcGtnIG9yIHNvbWV0aGluZyB0aGF0IEkgY2FuIGVhc2lseSBkZXBsb3kuCj4gPgo+ID4g VGhlcmUgc2hvdWxkIGJlIGEgInBsYXRmb3JtLTxuYW1lPi9wYWNrYWdlcy9nbGliY18yLjE2LjBf Ki5pcGsiIHdoaWNoCj4gPiBjb3VsZCBkbyB0aGlzIGpvYi4KPgo+IFBlcmZlY3QsIHRoaXMgaXMg KGFsbW9zdCkgd2hhdCBJIG5lZWQuIFRoYW5rIHlvdS4KPgo+IEkgdGhpbmsgcHR4ZGlzdCBpbnN0 YWxscyBpcGtnIHV0aWxzIG9uIHRoZSBob3N0IGJ5IGRlZmF1bHQsIGJ1dCBJIGNhbm5vdAo+IGZp bmQgdGhlbS4gUGVyaGFwcyBpdCBpcyBhIHByaXZhdGUgY29weT8KCj8KCiQgbCBwbGF0Zm9ybS08 bmFtZT4vc3lzcm9vdC1ob3N0L2Jpbi9vcGtnCi1yd3hyLXhyLXggMiBqYmUgcHR4IDM4ODI0IEp1 bCAxOSAxNTozNCBwbGF0Zm9ybS08bmFtZT4vc3lzcm9vdC1ob3N0L2Jpbi9vcGtnCgpIT1NUX1BB Q0tBR0VfTUFOQUdFTUVOVF9PUEtHPXkgKGFuZCB0aHVzIEhPU1RfT1BLRz15IGFuZCBIT1NUX09Q S0dfVVRJTFM9eQotPiBidXQgSSdtIHVzaW5nIHB0eGRpc3QgbWFzdGVyKQoKQW5kIHRoaXMgSVBL LXBhY2thZ2UgKCJwbGF0Zm9ybS08bmFtZT4vcGFja2FnZXMvZ2xpYmNfMi4xNi4wXyouaXBrIikg aXMKZ2VuZXJhdGVkIGJ5IHRoZSByZWd1bGFyIHJ1bGUgInJ1bGVzL2dsaWJjLm1ha2UiIGZvciBl dmVyeSBQVFhkaXN0IHByb2plY3QuCgpDaGVlcnMsCkp1ZXJnZW4KCi0tIApQZW5ndXRyb25peCBl LksuIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgfCBKdWVyZ2Vu IEJvcmxlaXMgwqAgwqAgwqAgwqAgwqAgwqAgfApJbmR1c3RyaWFsIExpbnV4IFNvbHV0aW9ucyDC oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHwgaHR0cDovL3d3dy5wZW5ndXRyb25peC5kZS8g wqB8CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpwdHhk aXN0IG1haWxpbmcgbGlzdApwdHhkaXN0QHBlbmd1dHJvbml4LmRl From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-vk0-x234.google.com ([2607:f8b0:400c:c05::234]) by metis.ext.pengutronix.de with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bUslO-0003EN-H8 for ptxdist@pengutronix.de; Wed, 03 Aug 2016 11:46:58 +0200 Received: by mail-vk0-x234.google.com with SMTP id n129so141551882vke.3 for ; Wed, 03 Aug 2016 02:46:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160803093730.mdkkudinj7inrwjm@pengutronix.de> References: <20160803080437.GG11824@pengutronix.de> <20160803093730.mdkkudinj7inrwjm@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Wed, 3 Aug 2016 11:46:51 +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="===============0818010701==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============0818010701== Content-Type: multipart/alternative; boundary=94eb2c094e68837955053927b606 --94eb2c094e68837955053927b606 Content-Type: text/plain; charset=UTF-8 2016-08-03 11:37 GMT+02:00 Robert Schwebel : > On Wed, Aug 03, 2016 at 10:04:37AM +0200, Michael Olbrich wrote: > > 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. > > Can you elaborate why you need to patch the toolchain? If it's of > general interest, we might be interested in the patches. > Hi Robert, I need to deploy a hotfix for a known glibc bug that affected glibc-2.16. This will not be needed for more recent glibc versions. Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --94eb2c094e68837955053927b606 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2016-08-03 11:37 GMT+02:00 Robert Schwebel <r.schwebel@pengutr= onix.de>:
= On Wed, Aug 03, 2016 at 10:04:37AM +0200, Michael Olbrich wrote:
> On Tue, Aug 02, 2016 at 07:06:55PM +0200, Guillermo Rodriguez Garcia w= rote:
> > 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 t= he
> > toolchain. What is the best way to generate a patched glibc witho= ut
> > recompiling the toolchain ? Is there a recommended procedure for = this?
>
> There is no procedure for this. The libc is part of toolchain, and mix= ing
> 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.

Can you elaborate why you need to patch the toolchain? If it's o= f
general interest, we might be interested in the patches.

Hi Robert,

I need to deploy a ho= tfix for a known glibc bug that affected glibc-2.16. This will not be neede= d for more recent glibc versions.

Guillermo Rodriguez Garc= ia
guill= e.rodriguez@gmail.com
--94eb2c094e68837955053927b606-- --===============0818010701== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0818010701==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <201608031206.46603.jbe@pengutronix.de> References: <20160803080437.GG11824@pengutronix.de> <201608031206.46603.jbe@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Wed, 3 Aug 2016 13:29:07 +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="===============0588535078==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: Juergen Borleis Cc: "ptxdist@pengutronix.de" --===============0588535078== Content-Type: multipart/alternative; boundary=001a113ab81a4545980539292412 --001a113ab81a4545980539292412 Content-Type: text/plain; charset=UTF-8 Hello, 2016-08-03 12:06 GMT+02:00 Juergen Borleis : > Hi, > > On Wednesday 03 August 2016 11:45:57 Guillermo Rodriguez Garcia wrote: > > 2016-08-03 10:04 GMT+02:00 Michael Olbrich : > > > 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. > > There should be a "platform-/packages/glibc_2.16.0_*.ipk" which > could do > this job. > Perfect, this is (almost) what I need. Thank you. I think ptxdist installs ipkg utils on the host by default, but I cannot find them. Perhaps it is a private copy? -- Guillermo Rodriguez Garcia guille.rodriguez@gmail.com 2016-08-03 12:06 GMT+02:00 Juergen Borleis : > Hi, > > On Wednesday 03 August 2016 11:45:57 Guillermo Rodriguez Garcia wrote: > > 2016-08-03 10:04 GMT+02:00 Michael Olbrich : > > > 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. > > There should be a "platform-/packages/glibc_2.16.0_*.ipk" which > could do > this job. > > Cheers > Juergen > > -- > Pengutronix e.K. | Juergen Borleis > | > Industrial Linux Solutions | http://www.pengutronix.de/ > | > -- Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a113ab81a4545980539292412 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

2016-08-03 12:06 GMT+02:00 Juergen Borleis <jbe@pengutronix.de&= gt;:
Hi,

On Wednesday 03 August 2016 11:45:57 Guillermo Rodriguez Garcia wrote:
> 2016-08-03 10:04 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > 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 BS= P. 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, an= d mixing
> > different versions is not a good idea.
> > And at least with an OSELAS.Toolchain, rebuilding it isn't re= ally a
> > problem. It's just a PTXdist project.
>
> Thank you for your answer. Probably I did not explain my problem corre= ctly.
> Rebuilding the toolchain per se is not a problem; the problem is how t= o
> deploy the patched library. The process of rebuilding the toolchain > basically installs the (fixed) toolchain in my development machine. Th= is 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 th= e
> 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.

There should be a "platform-<name>/packages/glibc_2.16.0_= *.ipk" which could do
this job.

Perfect, this is (almost) wha= t I need. Thank you.

I think ptxdist installs ipkg= utils on the host by default, but I cannot find them. Perhaps it is a priv= ate copy?=C2=A0

--
Guillermo Rodriguez Garcia
guille.rodriguez= @gmail.com

2016-= 08-03 12:06 GMT+02:00 Juergen Borleis <jbe@pengutronix.de>:=
Hi,

On Wednesday 03 August 2016 11:45:57 Guillermo Rodriguez Garcia wrote:
> 2016-08-03 10:04 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > 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 BS= P. 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, an= d mixing
> > different versions is not a good idea.
> > And at least with an OSELAS.Toolchain, rebuilding it isn't re= ally a
> > problem. It's just a PTXdist project.
>
> Thank you for your answer. Probably I did not explain my problem corre= ctly.
> Rebuilding the toolchain per se is not a problem; the problem is how t= o
> deploy the patched library. The process of rebuilding the toolchain > basically installs the (fixed) toolchain in my development machine. Th= is 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 th= e
> 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.

There should be a "platform-<name>/packages/glibc_2.16.0_= *.ipk" which could do
this job.

Cheers
Juergen

--
Pengutronix e.K. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Juergen Borleis =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
Industrial Linux Solu= tions =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= | http://www.pengutronix.de/ =C2=A0|



--
=
Guillermo= Rodriguez Garcia
guille.rodriguez@gmail.com
--001a113ab81a4545980539292412-- --===============0588535078== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0588535078==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Borleis Date: Wed, 3 Aug 2016 12:06:46 +0200 References: <20160803080437.GG11824@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201608031206.46603.jbe@pengutronix.de> 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de Cc: Guillermo Rodriguez Garcia SGksCgpPbiBXZWRuZXNkYXkgMDMgQXVndXN0IDIwMTYgMTE6NDU6NTcgR3VpbGxlcm1vIFJvZHJp Z3VleiBHYXJjaWEgd3JvdGU6Cj4gMjAxNi0wOC0wMyAxMDowNCBHTVQrMDI6MDAgTWljaGFlbCBP bGJyaWNoIDxtLm9sYnJpY2hAcGVuZ3V0cm9uaXguZGU+Ogo+ID4gT24gVHVlLCBBdWcgMDIsIDIw MTYgYXQgMDc6MDY6NTVQTSArMDIwMCwgR3VpbGxlcm1vIFJvZHJpZ3VleiBHYXJjaWEgd3JvdGU6 Cj4gPiA+IEkgbmVlZCB0byBpbmNsdWRlIGEgcGF0Y2hlZCB2ZXJzaW9uIG9mIGdsaWJjIGluIGEg cHR4ZGlzdCBCU1AuIEkga25vdwo+ID4gPiB0aGF0IGdsaWJjIGl0c2VsZiBpcyBub3QgY29tcGls ZWQgYXMgcGFydCBvZiB0aGUgQlNQLCBidXQgYXMgcGFydCBvZiB0aGUKPiA+ID4gdG9vbGNoYWlu LiBXaGF0IGlzIHRoZSBiZXN0IHdheSB0byBnZW5lcmF0ZSBhIHBhdGNoZWQgZ2xpYmMgd2l0aG91 dAo+ID4gPiByZWNvbXBpbGluZyB0aGUgdG9vbGNoYWluID8gSXMgdGhlcmUgYSByZWNvbW1lbmRl ZCBwcm9jZWR1cmUgZm9yIHRoaXM/Cj4gPgo+ID4gVGhlcmUgaXMgbm8gcHJvY2VkdXJlIGZvciB0 aGlzLiBUaGUgbGliYyBpcyBwYXJ0IG9mIHRvb2xjaGFpbiwgYW5kIG1peGluZwo+ID4gZGlmZmVy ZW50IHZlcnNpb25zIGlzIG5vdCBhIGdvb2QgaWRlYS4KPiA+IEFuZCBhdCBsZWFzdCB3aXRoIGFu IE9TRUxBUy5Ub29sY2hhaW4sIHJlYnVpbGRpbmcgaXQgaXNuJ3QgcmVhbGx5IGEKPiA+IHByb2Js ZW0uIEl0J3MganVzdCBhIFBUWGRpc3QgcHJvamVjdC4KPgo+IFRoYW5rIHlvdSBmb3IgeW91ciBh bnN3ZXIuIFByb2JhYmx5IEkgZGlkIG5vdCBleHBsYWluIG15IHByb2JsZW0gY29ycmVjdGx5Lgo+ IFJlYnVpbGRpbmcgdGhlIHRvb2xjaGFpbiBwZXIgc2UgaXMgbm90IGEgcHJvYmxlbTsgdGhlIHBy b2JsZW0gaXMgaG93IHRvCj4gZGVwbG95IHRoZSBwYXRjaGVkIGxpYnJhcnkuIFRoZSBwcm9jZXNz IG9mIHJlYnVpbGRpbmcgdGhlIHRvb2xjaGFpbgo+IGJhc2ljYWxseSBpbnN0YWxscyB0aGUgKGZp eGVkKSB0b29sY2hhaW4gaW4gbXkgZGV2ZWxvcG1lbnQgbWFjaGluZS4gVGhpcyBpcwo+IHBlcmZl Y3QgZm9yIHRoZSByZWd1bGFyIGRldmVsb3BtZW50IGN5Y2xlLCBob3dldmVyIGluIHRoaXMgY2Fz ZSB3aGF0IEkKPiByZWFsbHkgbmVlZCBpcyBhIHdheSB0byBkZXBsb3kgYSBob3RmaXggd2l0aCB0 aGUgcGF0Y2hlZCBsaWJyYXJ5IG9uIHRoZQo+IHRhcmdldCBzeXN0ZW1zICh0aGF0IGFyZSBhbHJl YWR5IHJ1bm5pbmcpLiBTbyBJIHdhcyBsb29raW5nIGZvciBhIHdheSB0bwo+IGdlbmVyYXRlIGFu IGlwa2cvb3BrZyBvciBzb21ldGhpbmcgdGhhdCBJIGNhbiBlYXNpbHkgZGVwbG95LgoKVGhlcmUg c2hvdWxkIGJlIGEgInBsYXRmb3JtLTxuYW1lPi9wYWNrYWdlcy9nbGliY18yLjE2LjBfKi5pcGsi IHdoaWNoIGNvdWxkIGRvIAp0aGlzIGpvYi4KCkNoZWVycwpKdWVyZ2VuCgotLSAKUGVuZ3V0cm9u aXggZS5LLiDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoHwgSnVl cmdlbiBCb3JsZWlzIMKgIMKgIMKgIMKgIMKgIMKgIHwKSW5kdXN0cmlhbCBMaW51eCBTb2x1dGlv bnMgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqB8IGh0dHA6Ly93d3cucGVuZ3V0cm9uaXgu ZGUvIMKgfAoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K cHR4ZGlzdCBtYWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bUrAL-0001j2-8Y for ptxdist@pengutronix.de; Wed, 03 Aug 2016 10:04:39 +0200 Received: from mol by pty.hi.pengutronix.de with local (Exim 4.84_2) (envelope-from ) id 1bUrAL-000639-1d for ptxdist@pengutronix.de; Wed, 03 Aug 2016 10:04:37 +0200 Date: Wed, 3 Aug 2016 10:04:37 +0200 From: Michael Olbrich Message-ID: <20160803080437.GG11824@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de SGksCgpPbiBUdWUsIEF1ZyAwMiwgMjAxNiBhdCAwNzowNjo1NVBNICswMjAwLCBHdWlsbGVybW8g Um9kcmlndWV6IEdhcmNpYSB3cm90ZToKPiBJIG5lZWQgdG8gaW5jbHVkZSBhIHBhdGNoZWQgdmVy c2lvbiBvZiBnbGliYyBpbiBhIHB0eGRpc3QgQlNQLiBJIGtub3cgdGhhdAo+IGdsaWJjIGl0c2Vs ZiBpcyBub3QgY29tcGlsZWQgYXMgcGFydCBvZiB0aGUgQlNQLCBidXQgYXMgcGFydCBvZiB0aGUK PiB0b29sY2hhaW4uIFdoYXQgaXMgdGhlIGJlc3Qgd2F5IHRvIGdlbmVyYXRlIGEgcGF0Y2hlZCBn bGliYyB3aXRob3V0Cj4gcmVjb21waWxpbmcgdGhlIHRvb2xjaGFpbiA/IElzIHRoZXJlIGEgcmVj b21tZW5kZWQgcHJvY2VkdXJlIGZvciB0aGlzPwoKVGhlcmUgaXMgbm8gcHJvY2VkdXJlIGZvciB0 aGlzLiBUaGUgbGliYyBpcyBwYXJ0IG9mIHRvb2xjaGFpbiwgYW5kIG1peGluZwpkaWZmZXJlbnQg dmVyc2lvbnMgaXMgbm90IGEgZ29vZCBpZGVhLgpBbmQgYXQgbGVhc3Qgd2l0aCBhbiBPU0VMQVMu VG9vbGNoYWluLCByZWJ1aWxkaW5nIGl0IGlzbid0IHJlYWxseSBhCnByb2JsZW0uIEl0J3MganVz dCBhIFBUWGRpc3QgcHJvamVjdC4KCk1pY2hhZWwKCi0tIApQZW5ndXRyb25peCBlLksuICAgICAg ICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfApJbmR1 c3RyaWFsIExpbnV4IFNvbHV0aW9ucyAgICAgICAgICAgICAgICAgfCBodHRwOi8vd3d3LnBlbmd1 dHJvbml4LmRlLyAgfApQZWluZXIgU3RyLiA2LTgsIDMxMTM3IEhpbGRlc2hlaW0sIEdlcm1hbnkg fCBQaG9uZTogKzQ5LTUxMjEtMjA2OTE3LTAgICAgfApBbXRzZ2VyaWNodCBIaWxkZXNoZWltLCBI UkEgMjY4NiAgICAgICAgICAgfCBGYXg6ICAgKzQ5LTUxMjEtMjA2OTE3LTU1NTUgfAoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBtYWlsaW5n IGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bUscE-0002NH-H8 for ptxdist@pengutronix.de; Wed, 03 Aug 2016 11:37:30 +0200 Received: from rsc by pty.hi.pengutronix.de with local (Exim 4.84_2) (envelope-from ) id 1bUscE-0000R7-9t for ptxdist@pengutronix.de; Wed, 03 Aug 2016 11:37:30 +0200 Date: Wed, 3 Aug 2016 11:37:30 +0200 From: Robert Schwebel Message-ID: <20160803093730.mdkkudinj7inrwjm@pengutronix.de> References: <20160803080437.GG11824@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20160803080437.GG11824@pengutronix.de> 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: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de T24gV2VkLCBBdWcgMDMsIDIwMTYgYXQgMTA6MDQ6MzdBTSArMDIwMCwgTWljaGFlbCBPbGJyaWNo IHdyb3RlOgo+IE9uIFR1ZSwgQXVnIDAyLCAyMDE2IGF0IDA3OjA2OjU1UE0gKzAyMDAsIEd1aWxs ZXJtbyBSb2RyaWd1ZXogR2FyY2lhIHdyb3RlOgo+ID4gSSBuZWVkIHRvIGluY2x1ZGUgYSBwYXRj aGVkIHZlcnNpb24gb2YgZ2xpYmMgaW4gYSBwdHhkaXN0IEJTUC4gSSBrbm93IHRoYXQKPiA+IGds aWJjIGl0c2VsZiBpcyBub3QgY29tcGlsZWQgYXMgcGFydCBvZiB0aGUgQlNQLCBidXQgYXMgcGFy dCBvZiB0aGUKPiA+IHRvb2xjaGFpbi4gV2hhdCBpcyB0aGUgYmVzdCB3YXkgdG8gZ2VuZXJhdGUg YSBwYXRjaGVkIGdsaWJjIHdpdGhvdXQKPiA+IHJlY29tcGlsaW5nIHRoZSB0b29sY2hhaW4gPyBJ cyB0aGVyZSBhIHJlY29tbWVuZGVkIHByb2NlZHVyZSBmb3IgdGhpcz8KPiAKPiBUaGVyZSBpcyBu byBwcm9jZWR1cmUgZm9yIHRoaXMuIFRoZSBsaWJjIGlzIHBhcnQgb2YgdG9vbGNoYWluLCBhbmQg bWl4aW5nCj4gZGlmZmVyZW50IHZlcnNpb25zIGlzIG5vdCBhIGdvb2QgaWRlYS4KPiBBbmQgYXQg bGVhc3Qgd2l0aCBhbiBPU0VMQVMuVG9vbGNoYWluLCByZWJ1aWxkaW5nIGl0IGlzbid0IHJlYWxs eSBhCj4gcHJvYmxlbS4gSXQncyBqdXN0IGEgUFRYZGlzdCBwcm9qZWN0LgoKQ2FuIHlvdSBlbGFi b3JhdGUgd2h5IHlvdSBuZWVkIHRvIHBhdGNoIHRoZSB0b29sY2hhaW4/IElmIGl0J3Mgb2YKZ2Vu ZXJhbCBpbnRlcmVzdCwgd2UgbWlnaHQgYmUgaW50ZXJlc3RlZCBpbiB0aGUgcGF0Y2hlcy4KCnJz YwotLSAKUGVuZ3V0cm9uaXggZS5LLiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAg ICAgICAgICAgICAgICAgICAgICAgIHwKSW5kdXN0cmlhbCBMaW51eCBTb2x1dGlvbnMgICAgICAg ICAgICAgICAgIHwgaHR0cDovL3d3dy5wZW5ndXRyb25peC5kZS8gIHwKUGVpbmVyIFN0ci4gNi04 LCAzMTEzNyBIaWxkZXNoZWltLCBHZXJtYW55IHwgUGhvbmU6ICs0OS01MTIxLTIwNjkxNy0wICAg IHwKQW10c2dlcmljaHQgSGlsZGVzaGVpbSwgSFJBIDI2ODYgICAgICAgICAgIHwgRmF4OiAgICs0 OS01MTIxLTIwNjkxNy01NTU1IHwKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCnB0eGRpc3QgbWFpbGluZyBsaXN0CnB0eGRpc3RAcGVuZ3V0cm9uaXguZGU=