I have been using NONMEM VI with the g77 Fortran compiler on a Dell laptop
running Vista since last year with no problems. After not using NONMEM for
some time, I tried to run a previously successful control file yesterday and
the job wouldn't run. I suspected that the problem might be with the g77
compiler so I attempted to test g77 installation by creating and running the
"hello.for" test file as described in the NONMEM installation instructions.
When I attempted to compile the file from a DOS command, I got the
following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x37
): u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x89
): u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the same
message again as shown above. As I have had a problem with bad RAM on the
laptop before, I tested the RAM and found that the ram was fine. I have no
idea what the message means. If anyone has had this experience before or
could offer a suggestion on what I might try to overcome the problem, I
would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
g77 Problem
7 messages
5 people
Latest: Jun 29, 2010
Lloyd,
the linker seems unable to find the library files to link them all
together with your code.
I suspect there are some environment variables missing on your system.
Open a DOS window and enter set
If you do not see a line that looks similar to
LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
that might well be the problem.
You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
Right-click on "My computer", select System Properties, Advanced,
Environment variables, and add the specs for your system.
Andreas
"Lloyd Whitfield" <lwsolutions
Sent by: owner-nmusers
06/28/2010 04:14 PM
To
<nmusers
cc
Subject
[NMusers] g77 Problem
I have been using NONMEM VI with the g77 Fortran compiler on a Dell laptop
running Vista since last year with no problems. After not using NONMEM
for some time, I tried to run a previously successful control file
yesterday and the job wouldn?t run. I suspected that the problem might be
with the g77 compiler so I attempted to test g77 installation by creating
and running the ?hello.for? test file as described in the NONMEM
installation instructions. When I attempted to compile the file from a DOS
command, I got the following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x37):
u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x89):
u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the
same message again as shown above. As I have had a problem with bad RAM on
the laptop before, I tested the RAM and found that the ram was fine. I
have no idea what the message means. If anyone has had this experience
before or could offer a suggestion on what I might try to overcome the
problem, I would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
The information of this email and in any file transmitted with it is strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this email is prohibited and may be unlawful. In such case, you should please notify the sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. For further information about Actelion please see our website at http://www.actelion.com
Lloyd,
the linker seems unable to find the library files to link them all
together with your code.
I suspect there are some environment variables missing on your system.
Open a DOS window and enter set
If you do not see a line that looks similar to
LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
that might well be the problem.
You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
Right-click on "My computer", select System Properties, Advanced,
Environment variables, and add the specs for your system.
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 04:14 PM
To
<[email protected]>
cc
Subject
[NMusers] g77 Problem
I have been using NONMEM VI with the g77 Fortran compiler on a Dell laptop
running Vista since last year with no problems. After not using NONMEM
for some time, I tried to run a previously successful control file
yesterday and the job wouldn?t run. I suspected that the problem might be
with the g77 compiler so I attempted to test g77 installation by creating
and running the ?hello.for? test file as described in the NONMEM
installation instructions. When I attempted to compile the file from a DOS
command, I got the following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x37):
u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+0x89):
u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the
same message again as shown above. As I have had a problem with bad RAM on
the laptop before, I tested the RAM and found that the ram was fine. I
have no idea what the message means. If anyone has had this experience
before or could offer a suggestion on what I might try to overcome the
problem, I would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
The information of this email and in any file transmitted with it is strictly
confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended recipient,
any copying, distribution or any other use of this email is prohibited and may
be unlawful. In such case, you should please notify the sender immediately and
destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state them
to be the views of the sender's company. For further information about Actelion
please see our website at http://www.actelion.com
Dear Lloyd
I suggest you to edit locally the path for bin and lib. I had a similar
problem with SADAPT depending on the compiler I was using (g95 in my
case).
You create a small script that includes the bin and lib path. For
example, here is the script I used to force g95 to work with sadapt. In
the set path, I had to both add the bin and lib path. This had to be
done with Vista bit not XP.
Best
Serge Guzy; PhD
President, CEO; POP_PHARM
www.poppharm.com
set
path=c:\sadapt\g95\bin;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32\4.0.3
set
library_path=c:\sadapt\g95\lib;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32
\4.0.3
Quoted reply history
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Lloyd Whitfield
Sent: Monday, June 28, 2010 9:53 AM
To: [email protected]
Subject: RE: [NMusers] g77 Problem
Andreas,
Good ideas. Unfortunately, I forgot to mention in my first email that I
checked the environment variables and I have
LIBRARY_PATH=c:\g77\lib (this is where I have g77 installed) and
C:\g77\bin is in the PATH.
Any other ideas will be appreciated.
Thanks,
Lloyd
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of [email protected]
Sent: Monday, June 28, 2010 11:15 AM
To: Lloyd Whitfield
Cc: [email protected]
Subject: Re: [NMusers] g77 Problem
Lloyd,
the linker seems unable to find the library files to link them all
together with your code.
I suspect there are some environment variables missing on your system.
Open a DOS window and enter set
If you do not see a line that looks similar to
LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
that might well be the problem.
You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
Right-click on "My computer", select System Properties, Advanced,
Environment variables, and add the specs for your system.
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 04:14 PM
To
<[email protected]>
cc
Subject
[NMusers] g77 Problem
I have been using NONMEM VI with the g77 Fortran compiler on a Dell
laptop
running Vista since last year with no problems. After not using NONMEM
for some time, I tried to run a previously successful control file
yesterday and the job wouldn?t run. I suspected that the problem might
be
with the g77 compiler so I attempted to test g77 installation by
creating
and running the ?hello.for? test file as described in the NONMEM
installation instructions. When I attempted to compile the file from a
DOS
command, I got the following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x37
):
u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x89
):
u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the
same message again as shown above. As I have had a problem with bad RAM
on
the laptop before, I tested the RAM and found that the ram was fine. I
have no idea what the message means. If anyone has had this experience
before or could offer a suggestion on what I might try to overcome the
problem, I would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
The information of this email and in any file transmitted with it is
strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this email is
prohibited and may be unlawful. In such case, you should please notify
the
sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by
letter.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorised
to
state them to be the views of the sender's company. For further
information
about Actelion please see our website at http://www.actelion.com
--
The information contained in this email message may
contain confidential or legally privileged information and is intended solely
for the use of the named recipient(s). No confidentiality or privilege is
waived or lost by any transmission error. If the reader of this message is
not the intended recipient, please immediately delete the e-mail and all
copies of it from your system, destroy any hard copies of it and notify the
sender either by telephone or return e-mail. Any direct or indirect use,
disclosure, distribution, printing, or copying of any part of this message is
prohibited. Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of XOMA.
The problem seems to be that Windows (Vista and others as well) cuts the
path after 1,023 (2**10-1) characters (!).
See
http://www.vistaheads.com/forums/microsoft-public-windows-vista-general/122099-path-being-truncated-help.html
and other discussions.
Thus, it is only via the path length that the order is relevant and moving
g77 in front might affect other programs...
Some programs seem to add their path each time they are installed without
checking if it exists already.
I had five identical entries for MinGW in my path, two for Matlab and
three for Monolix....
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 10:50 PM
To
<[email protected]>
cc
Subject
RE: [NMusers] g77 Problem
Hi Garry,
Putting c:\g77\bin at the beginning of the PATH statement did the trick. I
would have never though of doing that. I appreciate your help immensely.
Regards,
Lloyd
Lloyd Whitfield, PhD
President, LW Solutions, LLC
9207 Cambridge Dr
Saline, MI 48176
Phone: 734-786-2877
FAX: 734-944-2712
Cell: 734-649-4386
[email protected]
Quoted reply history
-----Original Message-----
From: Boswell,Garry,FORT WORTH,R&D [mailto:[email protected]]
Sent: Monday, June 28, 2010 4:18 PM
To: Lloyd Whitfield
Subject: RE: [NMusers] g77 Problem
Lloyd,
Lloyd,
I had the same problem as you describe running under Vista. It seems that
the order of the environmental variables seem to matter. When I moved the
path for the G77 files to the first item in the path statement, it worked.
I also only used the G77 path in the System variables areas, not in the
individual user variables area also.
Garry
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of Lloyd Whitfield
Sent: Monday, June 28, 2010 3:11 PM
To: [email protected]
Subject: RE: [NMusers] g77 Problem
Dear Serge,
Thank you for your suggestions. I directly edited the LIBRARY_PATH and
PATH
so that both would include c:\g77\bin and c:\g77\lib and rebooted the
computer. Unfortunately, this did not correct my problem. Thus, the
environment variables do not appear to be the problem.
What I can't figure out is why g77 does not work now while it did
previously. Reinstalling g77 didn't help either.
Any other ideas will be appreciated.
Thanks,
Lloyd
Lloyd Whitfield, PhD
President, LW Solutions, LLC
9207 Cambridge Dr
Saline, MI 48176
Phone: 734-786-2877
FAX: 734-944-2712
Cell: 734-649-4386
[email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of Serge Guzy
Sent: Monday, June 28, 2010 2:02 PM
To: Lloyd Whitfield; [email protected]
Subject: RE: [NMusers] g77 Problem
Dear Lloyd
I suggest you to edit locally the path for bin and lib. I had a similar
problem with SADAPT depending on the compiler I was using (g95 in my
case).
You create a small script that includes the bin and lib path. For
example, here is the script I used to force g95 to work with sadapt. In
the set path, I had to both add the bin and lib path. This had to be
done with Vista bit not XP.
Best
Serge Guzy; PhD
President, CEO; POP_PHARM
www.poppharm.com
set
path=c:\sadapt\g95\bin;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32\4.0.3
set
library_path=c:\sadapt\g95\lib;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32
\4.0.3
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Lloyd Whitfield
Sent: Monday, June 28, 2010 9:53 AM
To: [email protected]
Subject: RE: [NMusers] g77 Problem
Andreas,
Good ideas. Unfortunately, I forgot to mention in my first email that I
checked the environment variables and I have
LIBRARY_PATH=c:\g77\lib (this is where I have g77 installed) and
C:\g77\bin is in the PATH.
Any other ideas will be appreciated.
Thanks,
Lloyd
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of [email protected]
Sent: Monday, June 28, 2010 11:15 AM
To: Lloyd Whitfield
Cc: [email protected]
Subject: Re: [NMusers] g77 Problem
Lloyd,
the linker seems unable to find the library files to link them all
together with your code.
I suspect there are some environment variables missing on your system.
Open a DOS window and enter set
If you do not see a line that looks similar to
LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
that might well be the problem.
You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
Right-click on "My computer", select System Properties, Advanced,
Environment variables, and add the specs for your system.
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 04:14 PM
To
<[email protected]>
cc
Subject
[NMusers] g77 Problem
I have been using NONMEM VI with the g77 Fortran compiler on a Dell
laptop
running Vista since last year with no problems. After not using NONMEM
for some time, I tried to run a previously successful control file
yesterday and the job wouldn?t run. I suspected that the problem might
be
with the g77 compiler so I attempted to test g77 installation by
creating
and running the ?hello.for? test file as described in the NONMEM
installation instructions. When I attempted to compile the file from a
DOS
command, I got the following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x37
):
u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x89
):
u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the
same message again as shown above. As I have had a problem with bad RAM
on
the laptop before, I tested the RAM and found that the ram was fine. I
have no idea what the message means. If anyone has had this experience
before or could offer a suggestion on what I might try to overcome the
problem, I would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
The information of this email and in any file transmitted with it is
strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this email is
prohibited and may be unlawful. In such case, you should please notify
the
sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by
letter.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorised
to
state them to be the views of the sender's company. For further
information
about Actelion please see our website at http://www.actelion.com
--
The information contained in this email message may
contain confidential or legally privileged information and is intended
solely
for the use of the named recipient(s). No confidentiality or privilege is
waived or lost by any transmission error. If the reader of this message is
not the intended recipient, please immediately delete the e-mail and all
copies of it from your system, destroy any hard copies of it and notify
the
sender either by telephone or return e-mail. Any direct or indirect use,
disclosure, distribution, printing, or copying of any part of this message
is
prohibited. Any views expressed in this message are those of the
individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of XOMA.
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.
The information of this email and in any file transmitted with it is strictly
confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended recipient,
any copying, distribution or any other use of this email is prohibited and may
be unlawful. In such case, you should please notify the sender immediately and
destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state them
to be the views of the sender's company. For further information about Actelion
please see our website at http://www.actelion.com
Hi,
I'm glad to hear that Lloyd now has g77 working. However, there is clearly something else he should try to understand about his system.
By putting the g77 path at the beginning of the environment PATH variable this means that the operating system finds the one that Lloyd wanted to use (C:\g77\bin) but only because this path is found before some other path in the environment PATH. It seems there must be another installation of something resembling g77 that is defined in the PATH.
It might be worth while trying to find what this is. By adding the new g77 path at the beginning of the PATH this other hidden application may no longer work properly.
One place to start looking is in PHSTMinGW. This is the Pharsight installation of a Unix like environment with a C++ compiler. My guess is that the error below was caused by g77 finding a path to something in the PHSTMingW installation that could then not find the right link libraries that g77 needs.
> C:\nmvi2\run>g77 hello.for -o hello.exe
> Info: resolving __fmode by linking to __imp___fmode (auto-import)
> Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
> C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
> 0x37
> ):
> u
> ndefined reference to `__cpu_features_init'
Good luck!
Nick
Lloyd Whitfield wrote:
> Hi Garry,
>
> Putting c:\g77\bin at the beginning of the PATH statement did the trick. I
> would have never though of doing that. I appreciate your help immensely.
>
> Regards,
> Lloyd
>
> Lloyd Whitfield, PhD
> President, LW Solutions, LLC
> 9207 Cambridge Dr
> Saline, MI 48176
> Phone: 734-786-2877
> FAX: 734-944-2712
> Cell: 734-649-4386
> [email protected]
>
Quoted reply history
> -----Original Message-----
>
> From: Boswell,Garry,FORT WORTH,R&D [ mailto: [email protected] ] Sent: Monday, June 28, 2010 4:18 PM
>
> To: Lloyd Whitfield
> Subject: RE: [NMusers] g77 Problem
>
> Lloyd,
>
> Lloyd,
>
> I had the same problem as you describe running under Vista. It seems that
> the order of the environmental variables seem to matter. When I moved the
> path for the G77 files to the first item in the path statement, it worked.
> I also only used the G77 path in the System variables areas, not in the
> individual user variables area also.
>
> Garry
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Lloyd Whitfield
> Sent: Monday, June 28, 2010 3:11 PM
> To: [email protected]
> Subject: RE: [NMusers] g77 Problem
>
> Dear Serge,
>
> Thank you for your suggestions. I directly edited the LIBRARY_PATH and PATH
> so that both would include c:\g77\bin and c:\g77\lib and rebooted the
> computer. Unfortunately, this did not correct my problem. Thus, the
> environment variables do not appear to be the problem.
>
> What I can't figure out is why g77 does not work now while it did
> previously. Reinstalling g77 didn't help either.
>
> Any other ideas will be appreciated.
>
> Thanks,
> Lloyd
>
> Lloyd Whitfield, PhD
> President, LW Solutions, LLC
> 9207 Cambridge Dr
> Saline, MI 48176
> Phone: 734-786-2877
> FAX: 734-944-2712
> Cell: 734-649-4386
> [email protected]
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Serge Guzy
> Sent: Monday, June 28, 2010 2:02 PM
> To: Lloyd Whitfield; [email protected]
> Subject: RE: [NMusers] g77 Problem
>
> Dear Lloyd
> I suggest you to edit locally the path for bin and lib. I had a similar
> problem with SADAPT depending on the compiler I was using (g95 in my
> case).
> You create a small script that includes the bin and lib path. For
> example, here is the script I used to force g95 to work with sadapt. In
> the set path, I had to both add the bin and lib path. This had to be
> done with Vista bit not XP.
> Best
> Serge Guzy; PhD
> President, CEO; POP_PHARM
> www.poppharm.com
>
> set
> path=c:\sadapt\g95\bin;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32\4.0.3
> set
> library_path=c:\sadapt\g95\lib;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32
> \4.0.3
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Lloyd Whitfield
> Sent: Monday, June 28, 2010 9:53 AM
> To: [email protected]
> Subject: RE: [NMusers] g77 Problem
>
> Andreas,
>
> Good ideas. Unfortunately, I forgot to mention in my first email that I
> checked the environment variables and I have
> LIBRARY_PATH=c:\g77\lib (this is where I have g77 installed) and
> C:\g77\bin is in the PATH.
>
> Any other ideas will be appreciated.
>
> Thanks,
> Lloyd
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On
> Behalf Of [email protected]
> Sent: Monday, June 28, 2010 11:15 AM
> To: Lloyd Whitfield
> Cc: [email protected]
> Subject: Re: [NMusers] g77 Problem
>
> Lloyd,
>
> the linker seems unable to find the library files to link them all
> together with your code.
> I suspect there are some environment variables missing on your system.
> Open a DOS window and enter set
>
> If you do not see a line that looks similar to
> LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
> that might well be the problem.
> You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
>
> Right-click on "My computer", select System Properties, Advanced,
> Environment variables, and add the specs for your system.
>
> Andreas
>
> "Lloyd Whitfield" <[email protected]>
> Sent by: [email protected]
> 06/28/2010 04:14 PM
>
> To
> <[email protected]>
> cc
>
> Subject
> [NMusers] g77 Problem
>
> I have been using NONMEM VI with the g77 Fortran compiler on a Dell
> laptop
> running Vista since last year with no problems. After not using NONMEM
> for some time, I tried to run a previously successful control file
> yesterday and the job wouldn?t run. I suspected that the problem might
> be
> with the g77 compiler so I attempted to test g77 installation by
> creating
> and running the ?hello.for? test file as described in the NONMEM
> installation instructions. When I attempted to compile the file from a
> DOS
> command, I got the following:
>
> C:\nmvi2\run>g77 hello.for -o hello.exe
> Info: resolving __fmode by linking to __imp___fmode (auto-import)
> Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
> C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
> 0x37
> ):
> u
> ndefined reference to `__cpu_features_init'
> C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
> 0x89
> ):
> u
> ndefined reference to `_pei386_runtime_relocator'
> fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
> fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
> fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
> fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
> nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
> nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
> collect2: ld returned 1 exit status
>
> C:\nmvi2\run>
>
> I reinstalled the g77 compiler and ran the hello.for file and got the
> same message again as shown above. As I have had a problem with bad RAM
> on
> the laptop before, I tested the RAM and found that the ram was fine. I
>
> have no idea what the message means. If anyone has had this experience
> before or could offer a suggestion on what I might try to overcome the
> problem, I would be greatly appreciate any suggestions.
>
> Thanks,
> Lloyd Whitfield
>
> The information of this email and in any file transmitted with it is
> strictly confidential and may be legally privileged.
> It is intended solely for the addressee. If you are not the intended
> recipient, any copying, distribution or any other use of this email is
> prohibited and may be unlawful. In such case, you should please notify
> the
> sender immediately and destroy this email.
> The content of this email is not legally binding unless confirmed by
> letter.
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised
> to
> state them to be the views of the sender's company. For further
> information
> about Actelion please see our website at http://www.actelion.com
>
> --
> The information contained in this email message may
> contain confidential or legally privileged information and is intended
> solely
> for the use of the named recipient(s). No confidentiality or privilege is
> waived or lost by any transmission error. If the reader of this message is
> not the intended recipient, please immediately delete the e-mail and all
> copies of it from your system, destroy any hard copies of it and notify the
> sender either by telephone or return e-mail. Any direct or indirect use,
> disclosure, distribution, printing, or copying of any part of this message
> is
> prohibited. Any views expressed in this message are those of the individual
>
> sender, except where the message states otherwise and the sender is
> authorized to state them to be the views of XOMA.
>
> This e-mail (including any attachments) is confidential and may be legally
> privileged. If you are not an intended recipient or an authorized
> representative of an intended recipient, you are prohibited from using,
> copying or distributing the information in this e-mail or its attachments.
> If you have received this e-mail in error, please notify the sender
> immediately by return e-mail and delete all copies of this message and any
> attachments.
>
> Thank you.
--
Nick Holford, Professor Clinical Pharmacology
Dept Pharmacology & Clinical Pharmacology
University of Auckland,85 Park Rd,Private Bag 92019,Auckland,New Zealand
tel:+64(9)923-6730 fax:+64(9)373-7090 mobile:+64(21)46 23 53
email: [email protected]
http://www.fmhs.auckland.ac.nz/sms/pharmacology/holford
Hi Andreas,
The explanation you provide certainly sounds plausible. My laptop is
currently running the WinNonlin Validation Suite so I can not check my path
length to see if it is greater than 1,023 characters. I will check the path
length when the run is finished.
Thanks,
Lloyd
Lloyd Whitfield, PhD
President, LW Solutions, LLC
9207 Cambridge Dr
Saline, MI 48176
Phone: 734-786-2877
FAX: 734-944-2712
Cell: 734-649-4386
[email protected]
Quoted reply history
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, June 29, 2010 12:09 PM
To: Lloyd Whitfield
Cc: [email protected]
Subject: RE: [NMusers] g77 Problem
The problem seems to be that Windows (Vista and others as well) cuts the
path after 1,023 (2**10-1) characters (!).
See
http://www.vistaheads.com/forums/microsoft-public-windows-vista-general/1220
99-path-being-truncated-help.html
and other discussions.
Thus, it is only via the path length that the order is relevant and moving
g77 in front might affect other programs...
Some programs seem to add their path each time they are installed without
checking if it exists already.
I had five identical entries for MinGW in my path, two for Matlab and
three for Monolix....
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 10:50 PM
To
<[email protected]>
cc
Subject
RE: [NMusers] g77 Problem
Hi Garry,
Putting c:\g77\bin at the beginning of the PATH statement did the trick. I
would have never though of doing that. I appreciate your help immensely.
Regards,
Lloyd
Lloyd Whitfield, PhD
President, LW Solutions, LLC
9207 Cambridge Dr
Saline, MI 48176
Phone: 734-786-2877
FAX: 734-944-2712
Cell: 734-649-4386
[email protected]
-----Original Message-----
From: Boswell,Garry,FORT WORTH,R&D [mailto:[email protected]]
Sent: Monday, June 28, 2010 4:18 PM
To: Lloyd Whitfield
Subject: RE: [NMusers] g77 Problem
Lloyd,
Lloyd,
I had the same problem as you describe running under Vista. It seems that
the order of the environmental variables seem to matter. When I moved the
path for the G77 files to the first item in the path statement, it worked.
I also only used the G77 path in the System variables areas, not in the
individual user variables area also.
Garry
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of Lloyd Whitfield
Sent: Monday, June 28, 2010 3:11 PM
To: [email protected]
Subject: RE: [NMusers] g77 Problem
Dear Serge,
Thank you for your suggestions. I directly edited the LIBRARY_PATH and
PATH
so that both would include c:\g77\bin and c:\g77\lib and rebooted the
computer. Unfortunately, this did not correct my problem. Thus, the
environment variables do not appear to be the problem.
What I can't figure out is why g77 does not work now while it did
previously. Reinstalling g77 didn't help either.
Any other ideas will be appreciated.
Thanks,
Lloyd
Lloyd Whitfield, PhD
President, LW Solutions, LLC
9207 Cambridge Dr
Saline, MI 48176
Phone: 734-786-2877
FAX: 734-944-2712
Cell: 734-649-4386
[email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of Serge Guzy
Sent: Monday, June 28, 2010 2:02 PM
To: Lloyd Whitfield; [email protected]
Subject: RE: [NMusers] g77 Problem
Dear Lloyd
I suggest you to edit locally the path for bin and lib. I had a similar
problem with SADAPT depending on the compiler I was using (g95 in my
case).
You create a small script that includes the bin and lib path. For
example, here is the script I used to force g95 to work with sadapt. In
the set path, I had to both add the bin and lib path. This had to be
done with Vista bit not XP.
Best
Serge Guzy; PhD
President, CEO; POP_PHARM
www.poppharm.com
set
path=c:\sadapt\g95\bin;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32\4.0.3
set
library_path=c:\sadapt\g95\lib;c:\sadapt\g95\lib\gcc-lib\i686-pc-mingw32
\4.0.3
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Lloyd Whitfield
Sent: Monday, June 28, 2010 9:53 AM
To: [email protected]
Subject: RE: [NMusers] g77 Problem
Andreas,
Good ideas. Unfortunately, I forgot to mention in my first email that I
checked the environment variables and I have
LIBRARY_PATH=c:\g77\lib (this is where I have g77 installed) and
C:\g77\bin is in the PATH.
Any other ideas will be appreciated.
Thanks,
Lloyd
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On
Behalf Of [email protected]
Sent: Monday, June 28, 2010 11:15 AM
To: Lloyd Whitfield
Cc: [email protected]
Subject: Re: [NMusers] g77 Problem
Lloyd,
the linker seems unable to find the library files to link them all
together with your code.
I suspect there are some environment variables missing on your system.
Open a DOS window and enter set
If you do not see a line that looks similar to
LIBRARY_PATH=c:\g77\g77-2.95-mrg\lib
that might well be the problem.
You should also have an entry in PATH similar to c:\g77\g77-2.95-mrg\bin
Right-click on "My computer", select System Properties, Advanced,
Environment variables, and add the specs for your system.
Andreas
"Lloyd Whitfield" <[email protected]>
Sent by: [email protected]
06/28/2010 04:14 PM
To
<[email protected]>
cc
Subject
[NMusers] g77 Problem
I have been using NONMEM VI with the g77 Fortran compiler on a Dell
laptop
running Vista since last year with no problems. After not using NONMEM
for some time, I tried to run a previously successful control file
yesterday and the job wouldn?t run. I suspected that the problem might
be
with the g77 compiler so I attempted to test g77 installation by
creating
and running the ?hello.for? test file as described in the NONMEM
installation instructions. When I attempted to compile the file from a
DOS
command, I got the following:
C:\nmvi2\run>g77 hello.for -o hello.exe
Info: resolving __fmode by linking to __imp___fmode (auto-import)
Info: resolving __fpreset by linking to __imp___fpreset (auto-import)
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x37
):
u
ndefined reference to `__cpu_features_init'
C:/PHSTMinGW/bin/../lib/gcc/mingw32/3.4.5/../../../crt2.o:crt1.c:(.text+
0x89
):
u
ndefined reference to `_pei386_runtime_relocator'
fu000001.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000002.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000004.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
fu000005.o:(.idata$2+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o:(.idata$4+0x0): undefined reference to `_nm___fmode'
nmth000003.o:(.idata$4+0x0): undefined reference to `_nm___fpreset'
collect2: ld returned 1 exit status
C:\nmvi2\run>
I reinstalled the g77 compiler and ran the hello.for file and got the
same message again as shown above. As I have had a problem with bad RAM
on
the laptop before, I tested the RAM and found that the ram was fine. I
have no idea what the message means. If anyone has had this experience
before or could offer a suggestion on what I might try to overcome the
problem, I would be greatly appreciate any suggestions.
Thanks,
Lloyd Whitfield
The information of this email and in any file transmitted with it is
strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this email is
prohibited and may be unlawful. In such case, you should please notify
the
sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by
letter.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorised
to
state them to be the views of the sender's company. For further
information
about Actelion please see our website at http://www.actelion.com
--
The information contained in this email message may
contain confidential or legally privileged information and is intended
solely
for the use of the named recipient(s). No confidentiality or privilege is
waived or lost by any transmission error. If the reader of this message is
not the intended recipient, please immediately delete the e-mail and all
copies of it from your system, destroy any hard copies of it and notify
the
sender either by telephone or return e-mail. Any direct or indirect use,
disclosure, distribution, printing, or copying of any part of this message
is
prohibited. Any views expressed in this message are those of the
individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of XOMA.
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.
The information of this email and in any file transmitted with it is
strictly confidential and may be legally privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this email is
prohibited and may be unlawful. In such case, you should please notify the
sender immediately and destroy this email.
The content of this email is not legally binding unless confirmed by letter.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorised to
state them to be the views of the sender's company. For further information
about Actelion please see our website at http://www.actelion.com