public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.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 16:26:00 -0000	[thread overview]
Message-ID: <200911141128.27056.vapier@gentoo.org> (raw)
In-Reply-To: <200911141656.19709.yann.morin.1998@anciens.enib.fr>

[-- Attachment #1: Type: Text/Plain, Size: 1460 bytes --]

On Saturday 14 November 2009 10:56:19 Yann E. MORIN wrote:
> 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?

these are settings that should always be there and the user shouldnt be forced 
to configure themselves.  it also isnt specific to s390 ... it comes up with 
ppc targets too.

for the headers step, it's safe to export these all the time for all targets.  
we've been doing this in gentoo for quite a long time now.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-11-14 16:26 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
2009-11-14 16:26         ` Mike Frysinger [this message]
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=200911141128.27056.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=crossgcc@sourceware.org \
    --cc=h.grovsteen@tx.rr.com \
    --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).