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==--