public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Harold Grovesteen <h.grovsteen@tx.rr.com>
To: crossgcc@sourceware.org
Subject: [Fwd: Re: [PATCH 1 of 3] arch: s390 and 390x glibc patch]
Date: Wed, 11 Nov 2009 22:56:00 -0000	[thread overview]
Message-ID: <4AFB41D0.5050407@tx.rr.com> (raw)



-------- Original Message --------
Subject: 	Re: [PATCH 1 of 3] arch: s390 and 390x glibc patch
Date: 	Wed, 11 Nov 2009 16:48:23 -0600
From: 	Harold Grovesteen <h.grovsteen@tx.rr.com>
To: 	Mike Frysinger <vapier@gentoo.org>
References: 	<4dfd56aa6ad7b752b3c3.1257961228@dev.site> 
<200911111405.26910.vapier@gentoo.org>





Mike Frysinger wrote:

>On Wednesday 11 November 2009 12:40:28 Harold Grovesteen wrote:
>  
>
>>--- a/scripts/build/libc/glibc.sh	Fri Oct 30 20:08:44 2009 +0100
>>+++ b/scripts/build/libc/glibc.sh	Wed Nov 11 09:07:36 2009 -0600
>>@@ -152,7 +152,8 @@
>>     CT_DoExecLog ALL                                            \
>>     "${CT_SRC_DIR}/glibc-${cvs}${CT_LIBC_VERSION}/configure"    \
>>         --build="${CT_BUILD}"                                   \
>>-        --host="${CT_TARGET}"                                   \
>>+        --host="${CT_BUILD}"                                    \
>>+        --target="${CT_TARGET}"                                 \
>>    
>>
>
>not only is there no --target option for glibc, but it doesnt make any sense 
>for there to be one.  the C library doesnt generate code.
>
>setting the --host to the build system is also blatantly wrong.  i dont see 
>why you need either of these changes -- i cross-compile s390/s390x just fine 
>using the same method as all other targets.
>-mike
>
To both Mike and Yann, this goes to the issue I ran into with 
--with-long-double-128.  Mike, I am glad you can confirm that you don't 
need this.  Now, why did I?  Mike what version of glibc are you using?  
Maybe that is a factor.  I used glibc 2.9.

Mike, are you using crosstool-ng for s390/s390x or your own implementation?

I will make the other recommended changes and remove this.  If the 
problem with long-double-128 returns I will post the results for 
examination.

Thanks all,
Harold Grovesteen


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2009-11-11 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 22:56 Harold Grovesteen [this message]
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
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=4AFB41D0.5050407@tx.rr.com \
    --to=h.grovsteen@tx.rr.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).