Re: GNAT on MinGW

[Cesar Rabak <csrabak@yahoo.com.br>]

Vo, Anh (US SSA) escreveu:
> 
> -----Original Message-----
> From: comp.lang.ada-bounces@ada-france.org
> [mailto:comp.lang.ada-bounces@ada-france.org] On Behalf Of Cesar Rabak
> Sent: Thursday, March 01, 2007 4:37 PM
> To: comp.lang.ada@ada-france.org
> Subject: Re: GNAT on MinGW
> 
> << [...]
>> Way back I successfully built GNAT using cygwin. The problem was that
>>  the GNAT built did not support tasking run-time because GNAT under 
>> cygwin, used to build the newer GNAT, does not have tasking run-time 
>> support. Therefore, any Ada codes involving task will not run.
>>
>> Currently, I port MinGW/GNAT to cygwin and build gcc/gnat-4.1.2 using
>>  cygwin. The build hit a snap after going one fourth of the way. I 
>> scratch my hair with error message as shown below. I would be
>> thankful if any one can tell me what headers it looks for.
>>
>> [...]
> [snipped]
> 
>> The directory that should contain system headers does not exist: 
>> /mingw/include make[2]: *** [stmp-fixinc] Error 1 make[2]: Leaving
>> directory `/cygdrive/e/build-4.1.2/gcc' make[1]: *** [stage1_build]
>> Error 2 make[1]: Leaving directory `/cygdrive/e/build-4.1.2/gcc' 
>> make: *** [bootstrap] Error 2
>>
> It seems it has a hardcode "/mingw/include" path in some config file or
> some source (probably a header file generated by ./configure).
> 
> My quick shot for testing the hypotesis would be to add in fstab file a 
> mapping for /mingw/include to /usr/gnat/mingw32/include (which IIUC is 
> your path to the system include files).
> 
> I did similar to your suggestion by copying /mingw/include/ to /cygwin.
> This fixed got my build go much further, about 2/3 of the way. Again, I
> encountered two additional showstoppers. I managed to get by, surprised
> myself, these problems. The latest showstopper, as shown below, is a bit
> harder. It has some thing to do with adainit.c file. By the way, I am
> using Window 2000 instead of Window XP. I hope there is no difference
> between them regarding this problem.
> 
> [...]
> make[4]: Entering directory `/cygdrive/e/build-4.1.2/gcc/ada'
> make -C rts \
>                 CC="`echo \"/cygdrive/e/build-4.1.2/./gcc/xgcc
> -B/cygdrive/e/bui
> ld-4.1.2/./gcc/ -B/usr/local/mingw32/bin/ -B/usr/local/mingw32/lib/
> -isystem /us
> r/local/mingw32/include -isystem /usr/local/mingw32/sys-include\" \
>                 | sed -e 's,^\./xgcc,../../xgcc,' -e
> 's,-B\./,-B../../,'`" \
>                 INCLUDES="-I. -I.. -I../..
> -I/cygdrive/e/gcc-4.1.2/gcc/ada -I/cy
> gdrive/e/gcc-4.1.2/gcc/ada/../config
> -I/cygdrive/e/gcc-4.1.2/gcc/ada/../../inclu
> de -I/cygdrive/e/gcc-4.1.2/gcc/ada/.. -I./../.." \
>                 CFLAGS="-g -O2  -fexceptions -DIN_RTS" \
>                 srcdir=/cygdrive/e/gcc-4.1.2/gcc/ada \
>                 -f ../Makefile adaint.o argv.o cio.o cstreams.o ctrl_c.o
> errno.o
>  exit.o raise.o sysdep.o aux-io.o init.o initialize.o seh_init.o cal.o
> final.o t
> racebak.o expect.o mkdir.o socket.o raise-gcc.o
> make[5]: Entering directory `/cygdrive/e/build-4.1.2/gcc/ada/rts'
> /cygdrive/e/build-4.1.2/./gcc/xgcc -B/cygdrive/e/build-4.1.2/./gcc/
> -B/usr/local
> /mingw32/bin/ -B/usr/local/mingw32/lib/ -isystem
> /usr/local/mingw32/include -isy
> stem /usr/local/mingw32/sys-include -c -DIN_GCC   `echo -g -O2
> -fexceptions -DI
> N_RTS |sed -e 's/-pedantic//g' -e 's/-Wtraditional//g'`      -I. -I..
> -I../.. -I
> /cygdrive/e/gcc-4.1.2/gcc/ada -I/cygdrive/e/gcc-4.1.2/gcc/ada/../config
> -I/cygdr
> ive/e/gcc-4.1.2/gcc/ada/../../include -I/cygdrive/e/gcc-4.1.2/gcc/ada/..
> -I./../
> .. adaint.c \
>           -o adaint.o
> xgcc.exe: _spawnvp: No such file or directory

It seems the interim C compiler (xgcc.exe) was built in such a fashion 
the library for spanw* family of (C) functions was not linked in.

you can check this using 'nm'. Then, there are some things to try:

find in the makefile chain which one builds xgcc.exe and determine which 
library is being forgotten.

use another gcc as a replacement for xgcc in the makefile that builds 
adainit.o

These are interim solutions as obviouly these errors are symptoms of 
some configure not have worked flawlessly.