I attached the make.sys file produced by configure. When I used this file in compilation "Make. cannot load cpp. Stop" error message appears. When I used the Make.ia64 file "cannot execute /opt/langtools/lbin/cpp while compiling iotk_base.f90" message appers.
In both cases there is a complain about cpp compiler. Can you check whether cpp is installed properly just typing "cpp" in a command line. Bests, Eyvaz. ----- Orjinal Mesaj ----- Kimden: Andrea Ferretti Tarih: Tuesday, February 6, 2007 6:46 pm Konu: Re: [Pw_forum] compilation on itanium2 based HP-UX ia64 Kime: pw_forum at pwscf.org > > please, could you post the errors given by the compiler > and the make.sys file produced during configuration ?? > > andrea > > > Dear Dr. Isaev, > > I checked this file and also made several changes but it does > not work. > > > > Best regards, > > Gokhan > > > > ----- Orjinal Mesaj ----- > > Kimden: Eyvaz Isaev > > Tarih: Tuesday, February 6, 2007 2:54 pm > > Konu: Re: [Pw_forum] compilation on itanium2 based HP-UX ia64 > > Kime: pw_forum at pwscf.org > > > > > Hi Gokhan, > > > > > > Please have a look at /install/Make.ia64 file. > > > > > > Bests, > > > Eyvaz. > > > > > > ----- Original Message ---- > > > From: Gokhan GOKOGLU > > > To: pw_forum at pwscf.org > > > Sent: Tuesday, February 6, 2007 2:53:56 PM > > > Subject: [Pw_forum] compilation on itanium2 based HP-UX ia64 > > > > > > Dear all, > > > How can I compile the espresso 3.2 on a ia64 itanium2 based > HP- > > > UX machine? I tried many ways > > > but failed. Someone could help me ? > > > _______________________________________________ > > > Pw_forum mailing list > > > Pw_forum at pwscf.org > > > http://www.democritos.it/mailman/listinfo/pw_forum > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________> > > Do you Yahoo!? > > > Everyone is raving about the all-new Yahoo! Mail beta. > > > http://new.mail.yahoo.com > > > _______________________________________________ > > > Pw_forum mailing list > > > Pw_forum at pwscf.org > > > http://www.democritos.it/mailman/listinfo/pw_forum > > > > > > -- > > > This message has been scanned for viruses and > > > dangerous content by MailScanner, and is > > > believed to be clean. > > > > > > > > > _______________________________________________ > Pw_forum mailing list > Pw_forum at pwscf.org > http://www.democritos.it/mailman/listinfo/pw_forum > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > Dear Andrea, I attached the make.sys file produced by configure. When I used this file in compilation "Make. cannot load cpp. Stop" error message appears. When I used the Make.ia64 file "cannot execute /opt/langtools/lbin/cpp while compiling iotk_base.f90" message appers. Best regards, Gokhan ----- Orjinal Mesaj ----- Kimden: Andrea Ferretti Tarih: Tuesday, February 6, 2007 6:46 pm Konu: Re: [Pw_forum] compilation on itanium2 based HP-UX ia64 Kime: pw_forum at pwscf.org > > please, could you post the errors given by the compiler > and the make.sys file produced during configuration ?? > > andrea > > > Dear Dr. Isaev, > > I checked this file and also made several changes but it does > not work. > > > > Best regards, > > Gokhan > > > > ----- Orjinal Mesaj ----- > > Kimden: Eyvaz Isaev > > Tarih: Tuesday, February 6, 2007 2:54 pm > > Konu: Re: [Pw_forum] compilation on itanium2 based HP-UX ia64 > > Kime: pw_forum at pwscf.org > > > > > Hi Gokhan, > > > > > > Please have a look at /install/Make.ia64 file. > > > > > > Bests, > > > Eyvaz. > > > > > > ----- Original Message ---- > > > From: Gokhan GOKOGLU > > > To: pw_forum at pwscf.org > > > Sent: Tuesday, February 6, 2007 2:53:56 PM > > > Subject: [Pw_forum] compilation on itanium2 based HP-UX ia64 > > > > > > Dear all, > > > How can I compile the espresso 3.2 on a ia64 itanium2 based > HP- > > > UX machine? I tried many ways > > > but failed. Someone could help me ? > > > _______________________________________________ > > > Pw_forum mailing list > > > Pw_forum at pwscf.org > > > http://www.democritos.it/mailman/listinfo/pw_forum > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________> > > Do you Yahoo!? > > > Everyone is raving about the all-new Yahoo! Mail beta. > > > http://new.mail.yahoo.com > > > _______________________________________________ > > > Pw_forum mailing list > > > Pw_forum at pwscf.org > > > http://www.democritos.it/mailman/listinfo/pw_forum > > > > > > -- > > > This message has been scanned for viruses and > > > dangerous content by MailScanner, and is > > > believed to be clean. > > > > > > > > > _______________________________________________ > Pw_forum mailing list > Pw_forum at pwscf.org > http://www.democritos.it/mailman/listinfo/pw_forum > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > # make.sys. Generated from make.sys.in by configure. # compilation rules .SUFFIXES : .SUFFIXES : .o .c .f .f90 # most fortran compilers can directly preprocess c-like directives: use # $(MPIF90) $(F90FLAGS) -c $< # if explicit preprocessing by the C preprocessor is needed, use: # $(CPP) $(CPPFLAGS) $< -o $*.F90 # $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o # remember the tabulator in the first column !!! .f90.o: $(CPP) $(CPPFLAGS) $< -o $*.F90 $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o # .f.o and .c.o: do not modify .f.o: $(F77) $(FFLAGS) -c $< .c.o: $(CC) $(CFLAGS) -c $< # DFLAGS = precompilation options (possible arguments to -D and -U) # used by the C compiler and preprocessor # FDFLAGS = as DFLAGS, for the f90 compiler # See include/defs.h.README for a list of options and their meaning # With the exception of IBM xlf, FDFLAGS = $(DFLAGS) # For IBM xlf, FDFLAGS is the same as DFLAGS with separating commas DFLAGS = -D__FFTW -D__USE_INTERNAL_FFTW -D__MPI -D__PARA FDFLAGS = $(DFLAGS) # IFLAGS = how to locate directories where files to be included are # In most cases, IFLAGS = -I../include # If loading an external FFTW library, add the location of FFTW include files IFLAGS = -I../include # MODFLAGS = flag used by f90 compiler to locate modules # You need to search for modules in ./, in ../iotk/src, in ../Modules # Some applications also neeed modules in ../PW, ../PH, ../CPV MODFLAGS = -I./ -I../Modules -I../iotk/src \ -I../PW -I../PH -I../CPV # Compilers: fortran-90, fortran-77, C # If a parallel compilation is desired, MPIF90 should be a fortran-90 # compiler that produces executables for parallel execution using MPI # (such as for instance mpif90, mpf90, mpxlf90,...); # otherwise, an ordinary fortran-90 compiler (f90, g95, xlf90, ifort,...) # If you have a parallel machine but no suitable candidate for MPIF90, # try to specify the directory containing "mpif.h" in IFLAGS # and to specify the location of MPI libraries in MPI_LIBS MPIF90 = mpif90 #F90 = f90 CC = cc F77 = f90 # C preprocessor and preprocessing flags - for explicit preprocessing, # if needed (see the compilation rules above) # preprocessing flags must include DFLAGS and IFLAGS CPP = cpp CPPFLAGS = -P -traditional $(DFLAGS) $(IFLAGS) # compiler flags: C, F90, F77 # C flags must include DFLAGS and IFLAGS # F90 flags must include MODFLAGS, IFLAGS, and FDFLAGS with appropriate syntax CFLAGS = -O3 $(DFLAGS) $(IFLAGS) F90FLAGS = $(FFLAGS) $(FDFLAGS) $(IFLAGS) $(MODFLAGS) FFLAGS = -O # compiler flags without optimization for fortran-77 # the latter is NEEDED to properly compile dlamch.f, used by lapack FFLAGS_NOOPT = -O0 # Linker and linker-specific flags (if any) # Typically LD coincides with F90 or MPIF90 - not actually used # LD = mpif90 LDFLAGS = # External Libraries (if any) : blas, lapack, fft, MPI # If you have nothing better, use the local copy : ../flib/blas.a BLAS_LIBS = ../flib/blas.a # The following lapack libraries will be available in flib/ : # ../flib/lapack.a : contains all needed routines # ../flib/lapack_atlas.a: only routines not present in the Atlas library # For IBM machines with essl: load essl BEFORE lapack ! # remember that LAPACK_LIBS precedes BLAS_LIBS in loading order LAPACK_LIBS = -llapack # nothing needed here if the the internal copy of FFTW is compiled # (needs -D__FFTW -D__USE_INTERNAL_FFTW in DFLAGS) FFT_LIBS = # For parallel execution, the correct path to MPI libraries must # be specified in MPI_LIBS (except for IBM if you use mpxlf) MPI_LIBS = # IBM-specific: MASS libraries, if available and if -D__MASS is defined in FDFLAGS MASS_LIBS = # pgplot libraries (used by some post-processing tools) PGPLOT_LIBS = # ar command and flags - for most architectures: AR = ar, ARFLAGS = ruv # ARFLAGS_DYNAMICS is used in iotk to produce a dynamical library, # for Mac OS-X with PowerPC and xlf compiler. In all other cases # ARFLAGS_DYNAMICS = $(ARFLAGS) AR = ar ARFLAGS = ruv ARFLAGS_DYNAMIC= ruv # ranlib command. If ranlib is not needed (it isn't in most cases) use # RANLIB = echo RANLIB = ranlib # all internal and external libraries - do not modify LIBOBJS = ../flib/ptools.a ../flib/flib.a ../clib/clib.a ../iotk/src/libiotk.a LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FFT_LIBS) $(MPI_LIBS) $(MASS_LIBS) $(PGPLOT_LIBS) ____________________________________________________________________________________ Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/attachments/20070206/467a2c44/attachment.htm
