From: Ray Donnelly <mingw.android@gmail.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: [PATCH 1/3] binutils: Added ranlib to tools list
Date: Tue, 04 Feb 2014 08:33:00 -0000 [thread overview]
Message-ID: <CAOYw7dt=+DdnKAHNShfs6a+=7sS+DLQYkyxnQMAwmw7E7zqvgA@mail.gmail.com> (raw)
# HG changeset patch
# User Ray Donnelly <mingw.android@gmail.com>
# Date 1391499645 0
# Tue Feb 04 07:40:45 2014 +0000
# Node ID 2eab7ceda925402555d7d3107e5828734ac74c11
# Parent 529a71ea091e8ffa34d8b62f82e0996e3927750d
binutils: Added ranlib to tools list
so that it is available to available to
the core C compiler build because static
libraries are built and ranlib is used
on them.
Signed-off-by: Ray Donnelly <mingw.android@gmail.com>
diff -r 529a71ea091e -r 2eab7ceda925 scripts/build/binutils/binutils.sh
--- a/scripts/build/binutils/binutils.sh Thu Jan 16 14:55:23 2014 -0800
+++ b/scripts/build/binutils/binutils.sh Tue Feb 04 07:40:45 2014 +0000
@@ -106,13 +106,13 @@
fi
# Make those new tools available to the core C compilers to come.
- # Note: some components want the ${TARGET}-{ar,as,ld,strip} commands as
- # well. Create that.
+ # Note: some components want the ${TARGET}-{ar,as,ld,ranlib,strip} commands
+ # as well. Create that.
# Don't do it for canadian or cross-native, because the binutils
# are not executable on the build machine.
case "${CT_TOOLCHAIN_TYPE}" in
cross|native)
- binutils_tools=( ar as ld strip )
+ binutils_tools=( ar as ld ranlib strip )
if [ -n "${CT_ARCH_BINFMT_FLAT}" ]; then
binutils_tools+=( elf2flt flthdr )
fi
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2014-02-04 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 8:33 Ray Donnelly [this message]
2014-02-19 22:28 ` Yann E. MORIN
2014-02-04 8:42 [PATCH 1/3] " Ray Donnelly
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='CAOYw7dt=+DdnKAHNShfs6a+=7sS+DLQYkyxnQMAwmw7E7zqvgA@mail.gmail.com' \
--to=mingw.android@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).