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@xxxxxxxxxx> wrote: > "John P. Hartmann" <jphartmann@xxxxxxxxx> 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 >