From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Patched glibc in a ptxdist BSP
Date: Wed, 3 Aug 2016 10:04:37 +0200 [thread overview]
Message-ID: <20160803080437.GG11824@pengutronix.de> (raw)
In-Reply-To: <CABDcavZotsHae628NLqJu03qAiR+c3r8aR+vyNHssDPCo_SatA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-08-03 8:04 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 [this message]
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
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=20160803080437.GG11824@pengutronix.de \
--to=m.olbrich@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