mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas@biessmann.de>
To: PTXdsit ML <ptxdist@pengutronix.de>
Cc: OSELAS ML <oselas@community.pengutronix.de>
Subject: [ptxdist] [PATCH 0/7] OSELAS.Toolchain: add x86_64-unknown-linux-gnu glibc toolchain
Date: Sun, 12 Feb 2012 13:10:21 +0100	[thread overview]
Message-ID: <1329048628-70349-1-git-send-email-andreas@biessmann.de> (raw)

This series has an generic part to build a cross toolchain where build ==
host == target (add fake build type to HOST_CROSS_AUTOCONF) which is useful
for all toolchains.

The rest of this series is a 'pure64' x86_64-unknown-linux-gnu glibc
toolchain. The pure64 means that glibc's slibdir is set to /lib instead of
/lib64. Since we build for embedded systems it is not necessary to have
multilib-able toolchains. Additionally the '/lib - only' approach fits best to
current ptxdist way of building the rootfs.

Andreas Bießmann (7):
  add fake build type to HOST_CROSS_AUTOCONF
  architecture.in: add x86_64 arch
  add x86_64-unknown-linux-gnu configuration
  fixup_ptxconfigs.sh: add x86_64 target
  glibc-headers: prepare for x86_64 build
  gcc-4.6.2: add pure64 patch for x86_64
  glibc: force slibdir to /lib

 fixup_ptxconfigs.sh                                |    6 +
 .../0304-gcc-i386-use-pure64-CLFS-patch.patch      |   47 ++++++++
 patches/gcc-4.6.2/series                           |    3 +-
 ...utils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig |  118 ++++++++++++++++++++
 rules/architecture.in                              |    4 +
 rules/cross-gcc.make                               |    1 +
 rules/glibc-crt.make                               |    4 +-
 rules/glibc-first.make                             |    1 +
 rules/glibc-headers.make                           |    3 +
 rules/glibc.make                                   |    3 +
 rules/pre/toolchain.make                           |    2 +
 11 files changed, 189 insertions(+), 3 deletions(-)
 create mode 100644 patches/gcc-4.6.2/0304-gcc-i386-use-pure64-CLFS-patch.patch
 create mode 100644 ptxconfigs/x86_64-unknown-linux-gnu_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig

-- 
1.7.9


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2012-02-12 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 12:10 Andreas Bießmann [this message]
2012-02-12 12:10 ` [ptxdist] [PATCH 1/7] add fake build type to HOST_CROSS_AUTOCONF Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 2/7] architecture.in: add x86_64 arch Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 3/7] add x86_64-unknown-linux-gnu configuration Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 4/7] fixup_ptxconfigs.sh: add x86_64 target Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 5/7] glibc-headers: prepare for x86_64 build Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 6/7] gcc-4.6.2: add pure64 patch for x86_64 Andreas Bießmann
2012-02-12 12:10 ` [ptxdist] [PATCH 7/7] glibc: force slibdir to /lib Andreas Bießmann
2012-02-13  5:58 ` [ptxdist] [PATCH 0/7] OSELAS.Toolchain: add x86_64-unknown-linux-gnu glibc toolchain Klaus.Hachmeister
2012-02-13  7:36   ` Andreas Bießmann
2012-03-25 10:11 ` 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=1329048628-70349-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