This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: New Cygwin binary posted. was: help in creating gfortran windows binaries
- From: FX Coudert <fxcoudert at gmail dot com>
- To: Angelo Graziosi <Angelo dot Graziosi at roma1 dot infn dot it>
- Cc: Jerry DeLisle <jvdelisle at verizon dot net>, fortran at gcc dot gnu dot org
- Date: Sat, 27 Jan 2007 17:27:05 +0100
- Subject: Re: New Cygwin binary posted. was: help in creating gfortran windows binaries
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=fG7JxgzfZ1S1TXFJXaCgzrq+LTAqTsR/9iDgJh7V6ccP/M9AQNh4D98KjZcZ6rBqUD7wQmGMFRU2Pa6mxDuUC4rVF1P2QKBI88cX5X6OQBPvgUrygaIjGD0eDmNSUhE1001JhS3JjUvLaNgrc+1RmAN2PlJ+13qRrOaEXQr8NRw=
- References: <Pine.OSF.4.21.0701271659320.32259-100000@ax0rm1.roma1.infn.it>
I am building GFortran with YOUR configure options (--enable-
languages=c,
fortran --disable-libmudflap --enable-libgomp --disable-checking
--enable-threads --enable-werror) to see what happen, but it still
takes
almost 2 o 3 hours.
There's something easier to do: run "gfortran -v test.f90" from
Jerry's binaries: it will echo the exact command lines for the
subprocesses it spawns. The first one involves a binary named f951.
Run this (long) command line under gdb, by using:
" gdb -args /path/to/f951 ..." It wil start gdb, run the program.
Wait a bit, and then interrupt it with ^C (control-C). gdb will take
control, and you can ask it where the binary is hanging: type the
command "where" and report back the output here!
I hope the process is clear :) and I'm sorry if it's too detailed for
you, but don't know if you have any experience with gdb.
Thanks,
FX