This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wednesday 11 November 2009 12:40:28 Harold Grovesteen wrote: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.
--- 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
Thanks all, Harold Grovesteen
-- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |