mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Patched glibc in a ptxdist BSP
Date: Wed, 3 Aug 2016 15:46:34 +0200	[thread overview]
Message-ID: <CABDcavaVCJDK+PGnsCMg3myKy5Uo2yOVMBrevdcfJeb+ooA2aQ@mail.gmail.com> (raw)
In-Reply-To: <201608031448.29494.jbe@pengutronix.de>


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

      reply	other threads:[~2016-08-03 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 17:06 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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABDcavaVCJDK+PGnsCMg3myKy5Uo2yOVMBrevdcfJeb+ooA2aQ@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox