This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: libgfortran/mk-kinds-h.sh: Unknown type (cygwin)
- From: Tim Prince <timothyprince at sbcglobal dot net>
- To: tprince at myrealbox dot com
- Cc: Fortran List <fortran at gcc dot gnu dot org>
- Date: Sun, 17 Dec 2006 08:42:06 -0800
- Subject: Re: libgfortran/mk-kinds-h.sh: Unknown type (cygwin)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=lWV4YijmEK7NpEAaPpSkQpqvUj+zlGK+/yYo8d5sE84IX1ODxBZxxTI5uza/wnE0nUh+SE1pGi42ZZxkErBN+FP4oIzfcA3nlXwbjPkIBrsyIOBCWevUYU2WuNgzsdh0wM6wyqD8X7XrsKk7LWDulkUoICqMOQgqvtS4rdY2H34= ;
- References: <45854E32.9010402@sbcglobal.net>
- Reply-to: tprince at myrealbox dot com
Tim Prince wrote:
This failure has been present since mpfr-2.2.1 was adopted. Does it
stem from the lack of support for some of the tested types in the cygwin
headers? Are we supposed to figure it out by looking at some piece of
code?
Evident problems include command line corruption:
Dfile=generated/_log10_r10.F90 -I../../../libgfortran/m4 specific.m4 > ..
Where, apparently, an attempt is made to use ' ' as a replacement for
'/' (All references to files in libgfortran/m4 are like this)
and
/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../../libgfortran
-I. -iquote../../../libgfortran/io -I../../../libgfortran/../gcc
-I../../../lib
gfortran/../gcc/config -I../.././gcc -D_GNU_SOURCE -std=gnu99 -Wall
-Wstrict-pr
ototypes -Wmissing-prototypes -Wold-style-definition -Wextra
-Wwrite-strings -st
d=gnu99 -g -O2 -Wunknown-pragmas -c -o fmain.lo ../../../libgfortran/fmain.c
gcc -DHAVE_CONFIG_H -I. -I../../../libgfortran -I.
-iquote../../../libgfortran/i
o -I../../../libgfortran/../gcc -I../../../libgfortran/../gcc/config
-I../.././g
cc -D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wold
-style-definition -Wextra -Wwrite-strings -std=gnu99 -g -O2
-Wunknown-pragmas -c
../../../libgfortran/fmain.c -o fmain.o
Where it seems the -iquote option is expected to work without a
separator. Is this a Makefile generation problem? How should that work?
In addition, that -iquote is not supported by gcc 3.4.x such as the one
which comes with cygwin, so it may be necessary to run
make CC=<path to gcc 4.1 or newer> in the libgfortran build directory.
It looks like the gfortran build can be made to proceed by hacking away
at combinations of these issues.