RE: [NMusers] Gfortran problems in yosemite

From: Faelens, Ruben (Belgium) <"Faelens,>
Date: Tue, 23 Feb 2016 09:04:57 +0100

Dear Adedeji,

This is probably the cause of the problem:
Fatal Error: Cannot read module file 'fsizes.mod' opened at (1), because it=
 was created by a different version of GNU Fortran

Every time you install NONMEM, it will recompile the standard functions mod=
ules using your current compiler. Therefore, if you change compiler, you wi=
ll have to reinstall nonmem as well.

Kind regards,
Ruben Faelens

From: owner-nmusers_at_globomaxnm.com [mailto:owner-nmusers_at_globomaxnm.com] On=
 Behalf Of Adedeji Majekodunmi
Sent: maandag 22 februari 2016 23:28
To: nmusers_at_globomaxnm.com
Subject: RE: [NMusers] Gfortran problems in yosemite

Thanks for your informative replies. I've managed to fix this problem by un=
installing gfortran 5.2 version and installing the gfortran 4.9.2 and NONM=
EM now runs properly as it should (Thanks to Robert Bauer for the hints). M=
oving forward, I'll take on board all your useful comments.

Kind Regards,

Adedeji
________________________________
From: E.Olofsen_at_lumc.nl<mailto:E.Olofsen_at_lumc.nl>
To: majeko_at_hotmail.com<mailto:majeko_at_hotmail.com>; nmusers_at_globomaxnm.com<m=
ailto:nmusers_at_globomaxnm.com>
Subject: RE: [NMusers] Gfortran problems in yosemite
Date: Mon, 22 Feb 2016 21:12:45 +0000
Hi Adedeji,

This could happen if the "temp_dir" folder is present and still contains ou=
tput from a previous run with the previous compiler; the temporary folder m=
ay be emptied.

I hope this helps,

Erik
________________________________
From: owner-nmusers_at_globomaxnm.com<mailto:owner-nmusers_at_globomaxnm.com> [ow=
ner-nmusers_at_globomaxnm.com] on behalf of Adedeji Majekodunmi [majeko_at_hotmai=
l.com]
Sent: Monday, February 22, 2016 6:21 PM
To: nmusers_at_globomaxnm.com<mailto:nmusers_at_globomaxnm.com>
Subject: [NMusers] Gfortran problems in yosemite
Hi All,

I would be most grateful for any assistance with the following issues with =
NONMEM.
I'm using a mac (2012) and I've just recently upgraded to yosemite. The pro=
blem is that NONMEM has stopped running on my laptop since upgrading. This =
is fairly typical after an upgrade in mac and is usually a problem with gfo=
rtran compatibility which should normally be resolved by uninstalling and r=
e-installing gfortran with the following command:

sudo rm -r/usr/local/gfortran/usr/local/bin/gfortran

I've tried re-installing the 5.2 version of gfortran which is compatible wi=
th yosemite (https://gcc.gnu.org/wiki/GFortranBinaries#MacOS<https://redir.=
aspx?REF=z77EQi0w4RGD-4PtBbj2gBK2zBQcjtuzSIWPqYkEpJxdXP4qzDvTCAFodHRwczov=
L2djYy5nbnUub3JnL3dpa2kvR0ZvcnRyYW5CaW5hcmllcyNNYWNPUw..>).

I then tried running NONMEM but I'm getting the following errors:


 WARNINGS AND ERRORS (IF ANY) FOR PROBLEM 1

 (WARNING 2) NM-TRAN INFERS THAT THE DATA ARE POPULATION.

 (WARNING 13) WITH USER-WRITTEN PRED OR $PRED, NM-TRAN CANNOT APPEND THE
 MDV DATA ITEM.
Note: The following floating-point exceptions are signalling: IEEE_INVALID_=
FLAG IEEE_DIVIDE_BY_ZERO
Recompiling certain components
MUMODEL.f90:67:10:

       USE FSIZES, ONLY: F_PC,F_PG,F_LVO,F_LVS
          1
Fatal Error: Cannot read module file 'fsizes.mod' opened at (1), because it=
 was created by a different version of GNU Fortran
compilation terminated.
PRPNM.f90:58:10:

       USE PNM_CONFIG, ONLY: PNM_UPAR,M_IDEFD,M_IDEFA,M_EL,M_TQ,M_DAC,M_DPC
          1
Fatal Error: Cannot read module file 'pnm_config.mod' opened at (1), becaus=
e it was created by a different version of GNU Fortran
compilation terminated.
Building NONMEM Executable
gfortran: error: temp_dir/MUMODEL.o: No such file or directory
gfortran: error: temp_dir/PRPNM.o: No such file or directory
No nonmem execution.

It appears there are still problems with gfortran. Would anyone be kind eno=
ugh to assist?

My other question: Is there a way to prevent future upgrades on the mac int=
erfering with NONMEM?

Kind Regards,

Adedeji
PhD student, UCL.

Information in this email and any attachments is confidential and
intended solely for the use of the individual(s) to whom it is addressed
or otherwise directed. Please note that any views or opinions presented
in this email are solely those of the author and do not necessarily
represent those of the Company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The Company accepts no liability for any damage
caused by any virus transmitted by this email.
All SGS services are rendered in accordance with the applicable SGS
conditions of service available on request and accessible at
http://www.sgs.com/en/Terms-and-Conditions.aspx


Received on Tue Feb 23 2016 - 03:04:57 EST

This archive was generated by hypermail 2.3.0 : Fri Sep 27 2019 - 16:49:11 EDT