mpichbot
commented
7 years ago Originally by __ on 2008-10-30 14:40:10 -0500
This message has 2 attachment(s)
Closed mpichbot closed 7 years ago
mpichbot
commented
7 years ago Originally by __ on 2008-10-30 14:40:10 -0500
This message has 2 attachment(s)
mpichbot
commented
7 years ago Originally by __ on 2008-10-30 14:40:10 -0500
Attachment added: configure.log.gz (2.3 KiB)
Added by email2trac
mpichbot
commented
7 years ago Originally by __ on 2008-10-30 14:40:10 -0500
Attachment added: config.log.gz (13.6 KiB)
Added by email2trac
mpichbot
commented
7 years ago Originally by Rajeev Thakur on 2008-10-30 18:34:41 -0500
Set the environment variable F77 to ifort and then rerun configure.
Rajeev
> We try to install the 1.0.8 release including Fortran90 but
> we have an error during the configure step. We have already
> installed the previous versions 1.0.3 to 1.0.7 on the same
> Beowulf cluster with the same configure flags without any
> errors. Please, how we can fix this trouble?
>
> > configure: error: Unable to determine Fortran integer
> kinds for MPI > types. If you do not need Fortran 90, add
> --disable-f90 to the > configure options. If you need
> Fortran 90, please send the output > of configure and the
> file config.log to mpich2-maint@mcs.anl.gov .
Originally by __ on 2008-10-31 05:32:59 -0500
Hi Rajeev,
Thanks for your suggestion. As a summary of the mpich2 building of the
current 1.0.8 release, we have:
1) with the gfortran version of the system: it's crash.
# gfortran --version
GNU Fortran 95 (GCC) 4.1.0 20060515 (Red Hat 4.1.0-18)
2) with the current (beta) gortran release: it's OK.
$ gfortran-beta --version
GNU Fortran (GCC) 4.4.0 20081021 (experimental) [trunk revision 141258]
3) with ifort: it's OK.
# ifort --version
ifort (IFORT) 9.0 20051201
# cat /proc/version
Linux version 2.6.9-22.0.1.ELsmp (root@yort.fnal.gov) (gcc version
3.4.3 20050227 (Red Hat 3.4.3-22.1)) #1 SMP Thu Oct 27 10:53:36 CDT 2005
The related log files of the first two cases have in the tgz file.
Regards,
Jorge.
--
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Originally by __ on 2008-10-31 05:32:59 -0500
Attachment added: mpich2-gfortran.tgz (101.4 KiB)
Added by email2trac
mpichbot
commented
7 years ago Originally by Tobias Burnus on 2008-10-31 06:39:46 -0500
Hi,
jdelia@intec.unl.edu.ar wrote:
> Thanks for your suggestion. As a summary of the mpich2 building of the
> current 1.0.8 release, we have:
> 1) with the gfortran version of the system: it's crash.
> GNU Fortran 95 (GCC) 4.1.0 20060515 (Red Hat 4.1.0-18)
>
> 2) with the current (beta) gortran release: it's OK.
> GNU Fortran (GCC) 4.4.0 20081021 (experimental) [trunk revision 141258]
I'm not sure how to read that email (from a gfortran perspective). Is
this supposed to be a gfortran bug report?
From the GCC perspective only the following compilers are supported:
- Current release series, 4.3.2
- Previous release series, 4.2.4
- active development, 4.4.0
4.1.x was the first usable version of gfortran but 4.2.x and later
contain several bug fixes; especially the 4.1-Zero-Version was not in
the best shape. (Remember: gfortran was as new compiler added only with
4.0.0; unfortunately, it takes some time to iron out bugs.)
Additionally, note that bugs in older versions than the
active-development version (currently 4.4) will only be fixed if either
(a) it is a regression or (b) a serious bug (e.g. esp. wrong bugs) - but
only if the fix is simple. The reason is that one easily can introduce
regressions, which should never ever happen in the release branches.
I would suggest that you update to a newer compiler than 4.1.0 as you
seemingly did.
Some remarks:
- gzipping a TAR archive, which contains only gzipped files does not
make much sense; either only "tar" or tar-zip but then don't zip the
contained files.
- When reporting a bug, one needs more information, e.g. where to get
the source code, how it fails and how to reproduce it, etc. (A small
test case would also be handy.)
TobiasOriginally by __ on 2008-10-31 07:32:22 -0500
Hi Tobias,
Tobias Burnus <burnus@net-b.de> ha escrito:
> Hi,
>
> jdelia@intec.unl.edu.ar wrote:
>> Thanks for your suggestion. As a summary of the mpich2 building of the
>> current 1.0.8 release, we have:
>> 1) with the gfortran version of the system: it's crash.
>> GNU Fortran 95 (GCC) 4.1.0 20060515 (Red Hat 4.1.0-18)
>>
>> 2) with the current (beta) gortran release: it's OK.
>> GNU Fortran (GCC) 4.4.0 20081021 (experimental) [trunk revision 141258]
>
> I'm not sure how to read that email (from a gfortran perspective). Is
> this supposed to be a gfortran bug report?
No, I don't think so. It would to be seen as informative only for
other interested users.
> From the GCC perspective only the following compilers are supported:
> - Current release series, 4.3.2
> - Previous release series, 4.2.4
> - active development, 4.4.0
>
> 4.1.x was the first usable version of gfortran but 4.2.x and later
> contain several bug fixes; especially the 4.1-Zero-Version was not in
> the best shape. (Remember: gfortran was as new compiler added only with
> 4.0.0; unfortunately, it takes some time to iron out bugs.)
> Additionally, note that bugs in older versions than the
> active-development version (currently 4.4) will only be fixed if either
> (a) it is a regression or (b) a serious bug (e.g. esp. wrong bugs) - but
> only if the fix is simple. The reason is that one easily can introduce
> regressions, which should never ever happen in the release branches.
OK. I suspected this bug-fixing policy.
> I would suggest that you update to a newer compiler than 4.1.0 as you
> seemingly did.
Yes. We plain to do a system upgrade in this cluster.
> Some remarks:
> - gzipping a TAR archive, which contains only gzipped files does not
> make much sense; either only "tar" or tar-zip but then don't zip the
> contained files.
I am sorry. I relaxed with this redundancy.
> - When reporting a bug, one needs more information, e.g. where to get
> the source code, how it fails and how to reproduce it, etc. (A small
> test case would also be handy.)
Yes, I know this...
Regards,
Jorge.
--
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Originally by Rajeev Thakur on 2008-10-31 09:04:05 -0500
Jorge,
The tar file you just sent contains the g77-ifort version from
yesterday and gfortran-beta from today. The latter one was successful. It is
missing the gfortran version that failed.
Rajeev
> -----Original Message-----
> From: mpich2-bugs-bounces@mcs.anl.gov
> [mailto:mpich2-bugs-bounces@mcs.anl.gov] On Behalf Of mpich2
> Sent: Friday, October 31, 2008 5:33 AM
> To: undisclosed-recipients:
> Subject: Re: [mpich2-maint] #261: mpich2,1.0.8 release: a
> crash with Fortran90?
>
> -------------------------------------+------------------------
> ----------
> -------------------------------------+----
> Reporter: jdelia@intec.unl.edu.ar | Owner:
> Type: bug | Status: new
> Priority: major | Milestone:
> Component: mpich2 | Resolution:
> Keywords: |
> -------------------------------------+------------------------
> ----------
> -------------------------------------+----
>
>
> Comment (by ):
>
> {{{
>
> Hi Rajeev,
>
> Thanks for your suggestion. As a summary of the mpich2
> building of the current 1.0.8 release, we have:
>
> 1) with the gfortran version of the system: it's crash.
> # gfortran --version
> GNU Fortran 95 (GCC) 4.1.0 20060515 (Red Hat 4.1.0-18)
>
> 2) with the current (beta) gortran release: it's OK.
> $ gfortran-beta --version
> GNU Fortran (GCC) 4.4.0 20081021 (experimental) [trunk
> revision 141258]
>
> 3) with ifort: it's OK.
> # ifort --version
> ifort (IFORT) 9.0 20051201
>
> # cat /proc/version
> Linux version 2.6.9-22.0.1.ELsmp (root@yort.fnal.gov) (gcc version
> 3.4.3 20050227 (Red Hat 3.4.3-22.1)) #1 SMP Thu Oct 27
> 10:53:36 CDT 2005
>
> The related log files of the first two cases have in the tgz file.
>
> Regards,
> Jorge.
> --
Originally by __ on 2008-11-03 04:15:45 -0600
Dear Rajeev,
> The tar file you just sent contains the g77-ifort version from
> yesterday and gfortran-beta from today. The latter one was successful. It
> is missing the gfortran version that failed.
Forget it! I had a missing bad definition in my PATH with incompatible
versions of gcc and gfortran compilers. After to fix it, the
installation of the new 1.0.8 mpich2 release is OK with the native
compilers of the system distribution, i.e.
# gfortran --version
GNU Fortran 95 (GCC) 4.1.0 20060515 (Red Hat 4.1.0-18)
Copyright (C) 2006 Free Software Foundation, Inc.
# gcc --version
gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-3)
I include the related new output logs.
I'm sorry by the loud.
Thanks for your time.
Regards,
Jorge.
--
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Originally by __ on 2008-11-03 04:15:45 -0600
Attachment added: mpich2_1.0.8-gfortran_4.1.0_ok.tgz (35.7 KiB)
Added by email2trac
mpichbot
commented
7 years ago Originally by thakur on 2008-11-03 13:28:08 -0600
Looks like all is working well now. Resolving.
Originally by jdelia@intec.unl.edu.ar on 2008-10-30 14:40:10 -0500