From: Zhenqiang Chen <zhenqiang.chen@linaro.org>
To: yann.morin.1998@anciens.enib.fr
Cc: crossgcc@sourceware.org
Subject: [PATCH] libc/newlib: Add extra config for newlib
Date: Tue, 22 Nov 2011 11:25:00 -0000 [thread overview]
Message-ID: <4ECB8671.6070300@linaro.org> (raw)
# HG changeset patch
# User Zhenqiang Chen <zhenqiang.chen@linaro.org>
# Date 1321588050 -28800
# Node ID 00cde9fb9661f99d1fb62a935e56ac318b320668
# Parent a6c68712024f406df7d2da4af377f51982615833
libc/newlib: Add extra config for newlib.
So users can input config like --enable-newlib-register-fini.
Reviewed-by: Michael Hope
Signed-off-by: Zhenqiang Chen <zhenqiang.chen@linaro.org>
diff --git a/config/libc/newlib.in.2 b/config/libc/newlib.in.2
--- a/config/libc/newlib.in.2
+++ b/config/libc/newlib.in.2
@@ -35,3 +35,9 @@
_write... If you plan to port newlib to a new
platform/board, say Yes.
+config LIBC_NEWLIB_EXTRA_CONFIG_ARRAY
+ string
+ prompt "Extra config for newlib"
+ default ""
+ help
+ Extra flags to pass onto ./configure when configuring the newlib.
diff --git a/scripts/build/libc/newlib.sh b/scripts/build/libc/newlib.sh
--- a/scripts/build/libc/newlib.sh
+++ b/scripts/build/libc/newlib.sh
@@ -99,7 +99,8 @@
--host=${CT_BUILD} \
--target=${CT_TARGET} \
--prefix=${CT_PREFIX_DIR} \
- "${newlib_opts[@]}"
+ "${newlib_opts[@]}" \
+ "${CT_LIBC_NEWLIB_EXTRA_CONFIG_ARRAY[@]}"
CT_DoLog EXTRA "Building C library"
CT_DoExecLog ALL make ${JOBSFLAGS}
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2011-11-22 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 11:25 Zhenqiang Chen [this message]
2011-11-22 22:42 ` Yann E. MORIN
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=4ECB8671.6070300@linaro.org \
--to=zhenqiang.chen@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).