* [ptxdist] Patched glibc in a ptxdist BSP @ 2016-08-02 17:06 Guillermo Rodriguez Garcia 2016-08-03 8:04 ` Michael Olbrich 0 siblings, 1 reply; 9+ messages in thread From: Guillermo Rodriguez Garcia @ 2016-08-02 17:06 UTC (permalink / raw) To: ptxdist [-- Attachment #1.1: Type: text/plain, Size: 361 bytes --] 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 [-- Attachment #1.2: Type: text/html, Size: 586 bytes --] [-- Attachment #2: Type: text/plain, Size: 91 bytes --] _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-02 17:06 [ptxdist] Patched glibc in a ptxdist BSP Guillermo Rodriguez Garcia @ 2016-08-03 8:04 ` Michael Olbrich 2016-08-03 9:37 ` Robert Schwebel 2016-08-03 9:45 ` Guillermo Rodriguez Garcia 0 siblings, 2 replies; 9+ messages in thread From: Michael Olbrich @ 2016-08-03 8:04 UTC (permalink / raw) To: ptxdist 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. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 8:04 ` Michael Olbrich @ 2016-08-03 9:37 ` Robert Schwebel 2016-08-03 9:46 ` Guillermo Rodriguez Garcia 2016-08-03 9:45 ` Guillermo Rodriguez Garcia 1 sibling, 1 reply; 9+ messages in thread From: Robert Schwebel @ 2016-08-03 9:37 UTC (permalink / raw) To: ptxdist 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. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 9:37 ` Robert Schwebel @ 2016-08-03 9:46 ` Guillermo Rodriguez Garcia 0 siblings, 0 replies; 9+ messages in thread From: Guillermo Rodriguez Garcia @ 2016-08-03 9:46 UTC (permalink / raw) To: ptxdist [-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --] 2016-08-03 11:37 GMT+02:00 Robert Schwebel <r.schwebel@pengutronix.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 > 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 [-- Attachment #1.2: Type: text/html, Size: 1709 bytes --] [-- Attachment #2: Type: text/plain, Size: 91 bytes --] _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 8:04 ` Michael Olbrich 2016-08-03 9:37 ` Robert Schwebel @ 2016-08-03 9:45 ` Guillermo Rodriguez Garcia 2016-08-03 10:06 ` Juergen Borleis 1 sibling, 1 reply; 9+ messages in thread From: Guillermo Rodriguez Garcia @ 2016-08-03 9:45 UTC (permalink / raw) To: ptxdist [-- Attachment #1.1: Type: text/plain, Size: 1327 bytes --] Hi Michael, 2016-08-03 10:04 GMT+02:00 Michael Olbrich <m.olbrich@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 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 [-- Attachment #1.2: Type: text/html, Size: 1874 bytes --] [-- Attachment #2: Type: text/plain, Size: 91 bytes --] _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 9:45 ` Guillermo Rodriguez Garcia @ 2016-08-03 10:06 ` Juergen Borleis 2016-08-03 11:29 ` Guillermo Rodriguez Garcia 0 siblings, 1 reply; 9+ messages in thread From: Juergen Borleis @ 2016-08-03 10:06 UTC (permalink / raw) To: ptxdist; +Cc: Guillermo Rodriguez Garcia 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 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-<name>/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/ | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 10:06 ` Juergen Borleis @ 2016-08-03 11:29 ` Guillermo Rodriguez Garcia 2016-08-03 12:48 ` Juergen Borleis 0 siblings, 1 reply; 9+ messages in thread From: Guillermo Rodriguez Garcia @ 2016-08-03 11:29 UTC (permalink / raw) To: Juergen Borleis; +Cc: ptxdist [-- Attachment #1.1: Type: text/plain, Size: 3643 bytes --] Hello, 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 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-<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 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 <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 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-<name>/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 [-- Attachment #1.2: Type: text/html, Size: 5383 bytes --] [-- Attachment #2: Type: text/plain, Size: 91 bytes --] _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 11:29 ` Guillermo Rodriguez Garcia @ 2016-08-03 12:48 ` Juergen Borleis 2016-08-03 13:46 ` Guillermo Rodriguez Garcia 0 siblings, 1 reply; 9+ messages in thread From: Juergen Borleis @ 2016-08-03 12:48 UTC (permalink / raw) To: ptxdist; +Cc: Guillermo Rodriguez Garcia 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-<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 cannot > 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=y (and thus HOST_OPKG=y and HOST_OPKG_UTILS=y -> but I'm using ptxdist master) And this IPK-package ("platform-<name>/packages/glibc_2.16.0_*.ipk") is generated by the regular rule "rules/glibc.make" for every PTXdist project. Cheers, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ptxdist] Patched glibc in a ptxdist BSP 2016-08-03 12:48 ` Juergen Borleis @ 2016-08-03 13:46 ` Guillermo Rodriguez Garcia 0 siblings, 0 replies; 9+ messages in thread From: Guillermo Rodriguez Garcia @ 2016-08-03 13:46 UTC (permalink / raw) To: Juergen Borleis; +Cc: ptxdist [-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --] Hi Juergen, 2016-08-03 14:48 GMT+02:00 Juergen Borleis <jbe@pengutronix.de>: > 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-<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 cannot > > 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=y (and thus HOST_OPKG=y and HOST_OPKG_UTILS=y > -> but I'm using ptxdist master) > > And this IPK-package ("platform-<name>/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 [-- Attachment #1.2: Type: text/html, Size: 2251 bytes --] [-- Attachment #2: Type: text/plain, Size: 91 bytes --] _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2016-08-03 13:46 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2016-08-02 17:06 [ptxdist] Patched glibc in a ptxdist BSP Guillermo Rodriguez Garcia 2016-08-03 8:04 ` Michael Olbrich 2016-08-03 9:37 ` Robert Schwebel 2016-08-03 9:46 ` Guillermo Rodriguez Garcia 2016-08-03 9:45 ` Guillermo Rodriguez Garcia 2016-08-03 10:06 ` Juergen Borleis 2016-08-03 11:29 ` Guillermo Rodriguez Garcia 2016-08-03 12:48 ` Juergen Borleis 2016-08-03 13:46 ` Guillermo Rodriguez Garcia
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox