From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>,
Harold Grovesteen <h.grovsteen@tx.rr.com>
Subject: Re: [Fwd: Re: [PATCH 1 of 3] arch: s390 and 390x glibc patch]
Date: Sat, 14 Nov 2009 15:57:00 -0000 [thread overview]
Message-ID: <200911141656.19709.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <200911141023.19169.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Harold, Mike,
All,
On Saturday 14 November 2009 16:23:18 Mike Frysinger wrote:
> On Wednesday 11 November 2009 18:37:44 Harold Grovesteen wrote:
> > Mike Frysinger wrote:
> > >under Gentoo, a bunch of cache vars
> > >are forced just for the headers step as there is no compiler to test.
> > > those include mlong double tests.
> > > libc_cv_mlong_double_128=yes
> > > libc_cv_mlong_double_128ibm=yes
> > How do I achieve the equivalent of this with crosstool-ng?
> no idea. yann might know. just export those vars into the environment. this
> should be safe to do for all targets during the headers configure step only.
There is CT_LIBC_GLIBC_CONFIGPARMS that can be set in the menuconfig.
The value set in this variable is used to create a file named 'configparms'
in the top-level of the build dir. That file is then included from the
Makeconfig makefile.
It is possible to use it to pass one value. Passing more is not yet possible.
I can work something to handle more. Care to try the attached patch?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
[-- Attachment #2: ct-ng-many-configparms-values.patch --]
[-- Type: text/x-diff, Size: 1853 bytes --]
diff --git a/config/libc/glibc-eglibc.in-common b/config/libc/glibc-eglibc.in-common
--- a/config/libc/glibc-eglibc.in-common
+++ b/config/libc/glibc-eglibc.in-common
@@ -38,8 +38,8 @@
Unless you are building a toolchain for sh3/4, you should leave that empty.
- Note: this is awkward, and doesn't work well if you need more than one
- line in configparms
+ Note: If you need to pass more than one value, separate them with
+ '\n'. Eg.: var1=val1\nvar2=val2
config LIBC_GLIBC_EXTRA_CFLAGS
string
diff --git a/scripts/build/libc/glibc.sh b/scripts/build/libc/glibc.sh
--- a/scripts/build/libc/glibc.sh
+++ b/scripts/build/libc/glibc.sh
@@ -141,7 +141,7 @@
extra_config+=("$(do_libc_min_kernel_config)")
# Pre-seed the configparms file with values from the config option
- echo "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
+ printf "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
cross_cc=$(CT_Which "${CT_TARGET}-gcc")
CT_DoLog DEBUG "Using gcc for target: '${cross_cc}'"
@@ -309,7 +309,7 @@
CT_DoLog DEBUG "Extra CC args passed : '${extra_cc_args}'"
# Pre-seed the configparms file with values from the config option
- echo "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
+ printf "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
echo "libc_cv_forced_unwind=yes" > config.cache
echo "libc_cv_c_cleanup=yes" >> config.cache
@@ -418,7 +418,7 @@
CT_DoLog DEBUG "Extra CC args passed : '${extra_cc_args}'"
# Pre-seed the configparms file with values from the config option
- echo "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
+ printf "${CT_LIBC_GLIBC_CONFIGPARMS}" > configparms
# For glibc 2.3.4 and later we need to set some autoconf cache
# variables, because nptl/sysdeps/pthread/configure.in does not
[-- Attachment #3: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-11-14 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 22:56 Harold Grovesteen
2009-11-11 23:18 ` Mike Frysinger
[not found] ` <4AFB4AC8.2000103@tx.rr.com>
2009-11-14 15:21 ` Mike Frysinger
2009-11-14 15:57 ` Yann E. MORIN [this message]
2009-11-14 16:26 ` Mike Frysinger
2009-11-14 20:52 ` Harold Grovesteen
2009-11-15 1:12 ` Mike Frysinger
2009-11-15 0:37 ` Yann E. MORIN
2009-11-15 1:12 ` Mike Frysinger
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=200911141656.19709.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=h.grovsteen@tx.rr.com \
--cc=vapier@gentoo.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).