machine=AMD-64

5 messages 3 people Latest: Sep 28, 2005

machine=AMD-64

From: Johnson Rd 1 Date: September 28, 2005 technical
From: johnson.rd.1@pg.com Subject: machine=AMD-64 Date: Wed, 28 Sep 2005 13:35:35 -0400 We are trying to install NONMEN on a LINUX cluster and have been getting some compiler errors. The following information contains the error messages we are getting back from the compiler. If anyone has encounter this let us know the fix. THX OS=LINUX machine=AMD-64 Here are the error messages as well as the compilation failure messages. My concern is that we're giving it the "Intel" parameter when this is running and being compiled on an AMD-64 box. ===== Install ===== ./SETUP /app/nonmem f77 -o /usr/bin/ar Intel NONMEM V INSTALLATION UTILITY - UNIX CSH VERSION For instructions, see Appendix 4 of NONMEM Users Guide - Part III (NONMEM Installation Guide) NONMEM V directory is /app/nonmem Command for FORTRAN compiles is f77 Options for Fortran compiles is -o Command to build NONMEM archive is /usr/bin/ar Intel constants will be used To learn how to override the defaults, enter % SETUP help Continue (y/n) [y]? y Installing NONMEM V (Enter Ctrl-C to interrupt) ... Step 1. Make sub-directories of /app/nonmem Files have uppercase names - skipping step 2. Step 3. Copy NSIZES, PSIZES, etc. to sub-directories. Step 4a. Make changes to sep.f Step 4. Compile sep utility. Step 5. Separate files NMD, PPD1, PPD2, TRAN, and TRLD. Continue (y/n) [y]? y Step 5a. Separate NMD ... Make changes to BLKDAT.f ( original is BLKDAT.save ) Make changes to BEGIN.f (original is BEGIN.save ) Make changes to FLU.f (original is FLU.save ) Step 5b. Separate PPD1 and PPD2 ... Step 5c. Separate TRAN ... Step 5d. Separate TRLD ... Step 6. Compile source files *.f. Continue (y/n) [y]? y Step 6a. Compile NONMEM (this may take a while) ... Compilation failed. Please look for error messages in /app/nonmem/nm/emsgs.txt ===== Compiler Errors from /app/nonmem/nm/emsgs.txt ===== Tue Sep 27 13:55:10 EDT 2005 CN1.f: In subroutine `cn1': CN1.f:134: warning: 65 CALL SCALE (S,NV,OPSC) ^ Reference to unimplemented intrinsic `SCALE' at (^) (assumed EXTERNAL) CN.f: In subroutine `cn': CN.f:92: warning: 60 CALL SCALE (S,NV,OPSC) ^ Reference to unimplemented intrinsic `SCALE' at (^) (assumed EXTERNAL) GETETA.f: In subroutine `geteta': GETETA.f:45: warning: 1 ' SUBJECT DATA') ^ Missing comma in FORMAT statement at (^) INITL.f: In subroutine `initl': INITL.f:535: warning: 1 ' PRIOR') ^ Missing comma in FORMAT statement at (^) RESCL.f: In subroutine `rescl': RESCL.f:48: warning: CALL SCALE (S,N,1) ^ Reference to unimplemented intrinsic `SCALE' at (^) (assumed EXTERNAL) /tmp/ccY739tN.o(.text+0x47b): In function `commrg_': : undefined reference to `pred_' /tmp/ccY739tN.o(.text+0x1314): In function `commrg_': : undefined reference to `pred_' /tmp/ccY739tN.o(.text+0x1617): In function `commrg_': : undefined reference to `pred_' /tmp/ccMZPDsQ.o(.text+0x372): In function `final_': : undefined reference to `pred_' /tmp/ccJAqvQt.o(.text+0x1c76): In function `initl_': : undefined reference to `pred_' /tmp/ccJAqvQt.o(.text+0x2138): more undefined references to `pred_' follow collect2: ld returned 1 exit statusRobert D. Johnson, Ph.D. Procter and Gamble Pharmaceuticals Clinical Pharmacology and Pharmacokinetics (513) 622-1571

RE: machine=AMD-64

From: William Bachman Date: September 28, 2005 technical
From: "Bachman, William (MYD)" bachmanw@iconus.com Subject: [NMusers] RE: machine=AMD-64 Date: Wed, 28 Sep 2005 13:35:35 -0400 Bob, I see one minor error, the setup command should use a capital Oh for the optimization option instead of lowercase. ./SETUP /app/nonmem f77 -O /usr/bin/ar Intel However, I suspect that the real issue is use of a 64 bit system. We have one other client using a 64-bit HP box running HP-UX, they got SETUP to run, but the NONMEM test run (nmfe5 CONTROL5 report5) failed. Unfortunately, we don't have a 64-bit system for testing. nmconsult@globomaxnm.com GloboMax The Strategic Pharmaceutical Development Division of ICON plc 6031 University Blvd. Suite 300 Ellicott City, MD 21043 410-696-3098 voice 410-480-0776 fax

RE: machine=AMD-64

From: Darin Perusich Date: September 28, 2005 technical
From: Darin Perusich Darin.Perusich@cognigencorp.com Subject: [NMusers] RE: machine=AMD-64 Date: Wed, 28 Sep 2005 14:11:20 -0400 which distribution of linux are you running and which version of f77? you have to give SETUP the Intel parameter on the x86 archicture, it doesn't matter if the processors are intel or amd.

Re: RE: machine=AMD-64

From: Darin Perusich Date: September 28, 2005 technical
From: Darin Perusich Darin.Perusich@cognigencorp.com Subject: Re: [NMusers] RE: machine=AMD-64 Date: Wed, 28 Sep 2005 14:19:12 -0400 as long as the processor and OS (kernel) supports both 32 and 64 bit modes it's shouldn't matter. take sun microsystems sparc systems for example, they support both apps running in 32 bit and 64 bit modes and nonmem runs just fine as long as it's compiled for 32 bit.

Re: RE: machine=AMD-64

From: William Bachman Date: September 28, 2005 technical
From: "Bachman, William (MYD)" Subject: Re: [NMusers] RE: machine=AMD-64 Date: Wed, 28 Sep 2005 18:24:32 -0400 You are trying to use a GNU g77 optimization option (-O) with an Intel for Linux compiler. Determine the appropriate Intel for Linux compiler option and use in place of "-O". (Intel for Windows uses "/nologo /nbs /w /4Yportlib /Gs /Ob1gyti /Qprec_div" as an example). _______________________________________________________