From: "Andreas Bießmann" <andreas@biessmann.de>
To: OSELAS ML <oselas@community.pengutronix.de>
Cc: PTXdist ML <ptxdist@pengutronix.de>
Subject: [ptxdist] [PATCH 0/3] Build OSELAS.Toolchain on OS X
Date: Thu, 19 Jan 2012 09:50:48 +0100 [thread overview]
Message-ID: <1326963056-80149-1-git-send-email-andreas@biessmann.de> (raw)
These three little patches are required to build the OSELAS.Toolchain on OS X
Lion.
Currently only the
arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized
and
arm-v5te-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized
tested.
There are some build problems with i686 toolchain regarding building cross glibc
... but this is another task.
These patches where posted to the ptxdist ML previously, I don't know which is
the correct ML for OSELAS.Toolchain patches.
Andreas Bießmann (3):
glibc-headers: use freshly generated binutils
glibc-2.14.1: activate readelf detection
glibc-2.13: activate readelf detection
patches/glibc-2.13/autogen.sh | 8 ++++++++
patches/glibc-2.14.1/autogen.sh | 8 ++++++++
rules/glibc-headers.make | 5 +++++
3 files changed, 21 insertions(+), 0 deletions(-)
create mode 100755 patches/glibc-2.13/autogen.sh
create mode 100755 patches/glibc-2.14.1/autogen.sh
--
1.7.8.3
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-01-19 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 8:50 Andreas Bießmann [this message]
2012-01-19 8:50 ` [ptxdist] [PATCH 1/3] glibc-headers: use freshly generated binutils Andreas Bießmann
2012-01-19 8:50 ` [ptxdist] [PATCH 2/3] glibc-2.14.1: activate readelf detection Andreas Bießmann
2012-01-19 8:50 ` [ptxdist] [PATCH 3/3] glibc-2.13: " Andreas Bießmann
2012-01-25 13:43 ` Michael Olbrich
2012-01-26 9:43 ` Andreas Bießmann
2012-01-26 10:24 ` [ptxdist] [oselas] " Michael Olbrich
2012-01-26 10:37 ` Andreas Bießmann
2012-01-26 11:28 ` Michael Olbrich
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=1326963056-80149-1-git-send-email-andreas@biessmann.de \
--to=andreas@biessmann.de \
--cc=oselas@community.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