Hello Sébastien, and welcome,
* Sébastien Le Roux wrote on Sat, Jan 31, 2009 at 11:32:36PM CET:
>
> Thus I have a question concerning the behavior of the 'configuration'
> process, I would like to understand how does the AC_PROG_FC check for
> any Fortran compiler.
If you use AC_PROG_FC without
Hello Oguz,
* Oguz Yarimtepe wrote on Sat, Jan 31, 2009 at 10:21:44PM CET:
> ./configure --host="sh4-linux" --prefix="/st710x/usr/local/efls"
> --x-includes="/opt/STM/STLinux-2.2/devkit/sh4/target/usr/X11R7/include"
> --x-libraries="/opt/STM/STLinux-2.2/devkit/sh4/target/usr/X11R7/lib"
>
> make
[ resending to the list only, as some mail server thinks I am
sending inappropriate content to Sébastien; apologies for dupes ]
Hello Sébastien, and welcome,
* Sébastien Le Roux wrote on Sat, Jan 31, 2009 at 11:32:36PM CET:
>
> Thus I have a question concerning the behavior of the 'configuratio
Hello Stephen,
* Stephen P. Schaefer wrote on Fri, Jan 30, 2009 at 03:07:47AM CET:
> I'm seeing the following in config.log;
>
> configure:8972: checking for setpcred
> configure:9022: gcc -o conftest -O2 -march=i386 -mcpu=i686 -g -fpie
> -I/usr/kerberos/include -I/usr/kerberos/include/gssapi -Wa
Indeed so far I've seen that even if the first
F90 compiler that appears in my $PATH (env var) is not the GNU
fortran compiler (ie. ifort) the result of the AC_PROG_FC will be to
put FC="gfortran" ... how can this be possible ... the gfortran / f95
command of course appears in my $PATH but in
