From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Patching eglibc for AArch64
Date: Thu, 29 Nov 2012 12:19:40 +0100 [thread overview]
Message-ID: <50B744CC.4050906@linaro.org> (raw)
I would like to merge AArch64 eglibc support into OE-Core. As patch is
nearly 0.5MB I provide it in hrw/aarch64-support branch:
http://git.openembedded.org/openembedded-core-contrib/commit/?h=hrw/aarch64-support&id=aaa36e3ae6ff39682555ac6f21384b44d6f631e3
Commit adds two patches which add AArch64 support for 2.16 version of
eglibc. Both were merged upstream but with some alterations to fit into
trunk properly. As such trunk patches depend on other patches which can
alter state of other architectures which I prefer to avoid.
At Linaro we do daily builds of minimal, lamp, sdk images with this patch.
commit aaa36e3ae6ff39682555ac6f21384b44d6f631e3
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date: Wed Nov 21 17:08:13 2012 +0100
eglibc: add AArch64 support
Both patches are from libc-alpha mailing list and got merged into
eglibc/trunk. I can not use direct trunk commits because they already
depend on other changes.
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
meta/recipes-core/eglibc/eglibc-2.16/aarch64-glibc-fsf-v1-eaf6f205.patch | 15455 +
meta/recipes-core/eglibc/eglibc-2.16/aarch64-glibc-v3-elf.patch
| 47 +
meta/recipes-core/eglibc/eglibc_2.16.bb
| 6 +-
3 files changed, 15506 insertions(+), 2 deletions(-)
next reply other threads:[~2012-11-29 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 11:19 Marcin Juszkiewicz [this message]
2012-12-04 9:56 ` Patching eglibc for AArch64 Marcin Juszkiewicz
2012-12-04 10:49 ` Richard Purdie
2012-12-04 10:54 ` Marcin Juszkiewicz
2012-12-10 17:20 ` [PATCH] eglibc: add AArch64 support Marcin Juszkiewicz
2012-12-04 10:53 ` Patching eglibc for AArch64 Phil Blundell
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=50B744CC.4050906@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/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