Date: Sat, 9 Jun 2001 11:50:03 -0700 (PDT) From: Mark Pulford <mark@kyne.com.au> To: freebsd-ports@FreeBSD.org Subject: Re: ports/21941: MPI programs compiled with NAG F95 die with a SEGFAULT Message-ID: <200106091850.f59Io3p18501@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/21941; it has been noted by GNATS. From: Mark Pulford <mark@kyne.com.au> To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: ports/21941: MPI programs compiled with NAG F95 die with a SEGFAULT Date: Sun, 10 Jun 2001 04:17:05 +0930 Forwarded discussion with Andreas' permission. ----- Forwarded message from Andreas Schweitzer <andy@physast.uga.edu> ----- Date: Sat, 9 Jun 2001 14:20:13 -0400 From: Andreas Schweitzer <andy@physast.uga.edu> To: Mark Pulford <mark@kyne.com.au> Subject: Re: FreeBSD NAG/mpich problem, PR 21941 Reply-To: Andreas Schweitzer <andy@physast.uga.edu> X-Mailer: Mutt 0.95.6i In-Reply-To: <20010608192059.A15245@hamster.kyne.com.au>; from Mark Pulford on Fri, Jun 08, 2001 at 07:20:59PM +0930 Hi Mark, > I've just been looking through some old PRs without resolution and I > came across: > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21941 Thanks a lot for looking into this ! > I was wondering if you are still experiencing this problem, or if you > have more information? I've had a bit of a search around to see if > this has been noticed by anyone else. The most I've found is that > mpich is picky with how it gets compiled with fortran. Yes, that's the reason. It was indeed MPICH. Sorry to not report on that. I *think* the latest MPICH version has that fixed. However, it does not appear on the MPICH problem page. It has to do with argument passing and how the compiler gets called from the compiler wrapper. We got a fix from the MPICH folks. > > >From the information in your PR it seems like it is most likely a > problem between mpich & NAG. If you like, I can close this PR for you. Yes, it can be closed I dug out an e-mail with the fix and include it below Cheers Andreas <--------------- e-mail conversation with MPICH about the same bug ----------------------------> Date: Fri, 20 Oct 2000 18:43:25 -0400 From: Andreas Schweitzer <andy@physast.uga.edu> To: mpi-maint@mcs.anl.gov Cc: swider@mcs.anl.gov, Andreas Schweitzer <andy@bender.physast.uga.edu> Subject: Re: [MPI #5583] [swider@mcs.anl.gov: Possible bug in MPICH 1.2.1 with NAG F95 compiler on FreeBSD] Reply-To: Andreas Schweitzer <andy@physast.uga.edu> X-Mailer: Mutt 0.95.6i In-Reply-To: <200010181323.IAA30275@rose.mcs.anl.gov>; from Debbie Swider on Wed, Oct 18, 2000 at 08:23:41AM -0500 Thanks a lot for helping us. This does indeed work. We even have an alternate fix :-) Before the configure step one could do : export FXX_MODULE=" use f90_unix_env" export F77_GETARG="call getarg(i,arg=s)" export F77_IARGC="iargc()" then, it works, too. As far as we can see, the linker in FreeBSD 4.X changed significantly (in fact it improved), which seems to be resonsible for this. Thanks again Andreas Schweitzer On Wed, Oct 18, 2000 at 08:23:41AM -0500, Debbie Swider wrote: > > The problem is occurring in the call to 'rindex' in the function process_args. > > This function processes the command line arguments. Perhaps the problem is in > > the configuration of the NAG Fortran95 compiler with FreeBSD 4.1. It is > > possible that configure did not properly determine how Fortran should access > > command line arguments. > > Please replace do the following: > > 1) cd mpich-1.2.1/src/fortran/src > > 2) replace file farg.f with the following: > integer function mpir_iargc() > use f90_unix_env > mpir_iargc = iargc() > return > end > c > subroutine mpir_getarg( i, s ) > use f90_unix_env > integer i > character*(*) s > > call getarg(i,s) > return > end > > 3) return to the top-level mpich directory and type 'make' ( don't > reconfigure) > > Let me know what happens, > Debbie > ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106091850.f59Io3p18501>