From: "John P. Hartmann" <jphartmann@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: -m31 rejected when building libgcc for cross compiler for s390 (31 bit) gcc 4.6.0
Date: Sun, 22 May 2011 12:14:00 -0000 [thread overview]
Message-ID: <BANLkTikzyQr9zwypJfTEL3DR_Q1UgL9_9A@mail.gmail.com> (raw)
In-Reply-To: <mcrk4djz69a.fsf@coign.corp.google.com>
Thanks Ian.
http://wiki.osdev.org/GCC_Cross-Compiler suggested
--enable-languages=c,c++ --without-headers --disable-nls but that made
no difference. So I gave the target a symbolic link to /usr/include,
and then it failed in linking because of missing object decks. Seems
like the process is building something I didn't ask for, or at least
do not want.
What I am after is in fact a cross compiler to s390 os/360 object
(well, the variety that supports long ESD names--and not the old MVS
attempt.) As I already have a cross assembler, I guess I should
simply take the intermediary xgcc and run.
I did come across crosstool in my googling, as well as a number of
sites bemoaning the quality of documentation of gnu cross compiling.
On 22 May 2011 05:52, Ian Lance Taylor <iant@google.com> wrote:
> "John P. Hartmann" <jphartmann@gmail.com> writes:
>
>> Thanks, Ian. That brought me further, but still no cigar. Does the
>> following ring a bell?
>>
>> /usr/ports/gcc390/build460/./gcc/xgcc
>> -B/usr/ports/gcc390/build460/./gcc/
>> -B/usr/ports/gcc390/inst/s390-ibm-linux/bin/
>> -B/usr/ports/gcc390/inst/s390-ibm-linux/lib/ -isystem
>> /usr/ports/gcc390/inst/s390-ibm-linux/include -isystem
>> /usr/ports/gcc390/inst/s390-ibm-linux/sys-include -g -O2 -O2 -g
>> -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings
>> -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
>> -Wold-style-definition -isystem ./include -fPIC -g
>> -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
>> -fno-stack-protector -Dinhibit_libc -mlong-double-128 -I. -I.
>> -I../.././gcc -I/usr/src/gcc-4.6.0/libgcc
>> -I/usr/src/gcc-4.6.0/libgcc/. -I/usr/src/gcc-4.6.0/libgcc/../gcc
>> -I/usr/src/gcc-4.6.0/libgcc/../include
>> -I/usr/src/gcc-4.6.0/libgcc/../libdecnumber/dpd
>> -I/usr/src/gcc-4.6.0/libgcc/../libdecnumber -DHAVE_CC_TLS -o
>> decContext.o -MT decContext.o -MD -MP -MF decContext.dep -c
>> /usr/src/gcc-4.6.0/libgcc/../libdecnumber/decContext.c
>>
>> /usr/src/gcc-4.6.0/libgcc/../libdecnumber/decContext.c:33:43: fatal
>> error: string.h: No such file or directory
>> compilation terminated.
>
> string.h has to come from a C library. gcc does not include one.
>
> Since you are trying to build a cross-compiler to a GNU/Linux system,
> you may want to look at http://crosstool.org/ .
>
> Ian
>
next prev parent reply other threads:[~2011-05-22 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 12:22 John P. Hartmann
2011-05-21 17:04 ` Ian Lance Taylor
2011-05-22 2:00 ` John P. Hartmann
2011-05-22 8:58 ` Ian Lance Taylor
2011-05-22 9:34 ` Ian Lance Taylor
2011-05-22 9:44 ` Ian Lance Taylor
2011-05-22 12:14 ` John P. Hartmann [this message]
2011-05-22 13:12 ` Jeffrey Walton
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=BANLkTikzyQr9zwypJfTEL3DR_Q1UgL9_9A@mail.gmail.com \
--to=jphartmann@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).