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

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

  reply	other threads:[~2016-08-03 10:06 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 [this message]
2016-08-03 11:29       ` Guillermo Rodriguez Garcia
2016-08-03 12:48         ` Juergen Borleis
2016-08-03 13:46           ` Guillermo Rodriguez Garcia

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=201608031206.46603.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=guille.rodriguez@gmail.com \
    --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