[Users] problems with the Absoft compiler on Mac

Babiuc-Hamilton, Maria babiuc at marshall.edu
Wed May 14 15:27:21 CDT 2008 

Hi,

Yes. Here is the screen output:
________________________________________________________________________
Cactus - version: 4.0.b16
Reconfiguring wavetoy.
Adding configuration options from '/Users/mariababiuc/Cactus/configs/wavetoy/config-info'...
  Setting CC to 'gcc'
  Setting CXX to 'g++'
  Setting F77 to '/Applications/Absoft10.1/bin/f77'
  Setting F90 to '/Applications/Absoft10.1/bin/f95'
  Setting FPPFLAGS to '-Dminimise_outstanding_communications=moc_toolong -Duse_collective_communication_buffers=uccb_toolong'
End of options from '/Users/mariababiuc/Cactus/configs/wavetoy/config-info'.
Adding configuration options from user defaults...
End of options from user defaults.
creating cache ./config.cache
checking host system type... i386-apple-darwin8.11.1
checking whether make sets ${MAKE}... yes
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether the C++ compiler (g++  ) works... yes
checking whether the C++ compiler (g++  ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking for ranlib... ranlib
checking for cpp... /usr/bin/cpp
checking for cpp... /usr/bin/cpp
checking for perl... perl
checking for ar... ar
checking for mkdir... mkdir
checking for bash... /bin/sh
Unknown MacOS X f90 compiler.
Please add appropriate information to
/Users/mariababiuc/Cactus/lib/make/known-architectures/darwin
and send the updated file to CactusMaint
We will try anyway ...
checking how to run the C preprocessor... /usr/bin/cpp
checking for ANSI C header files... yes
checking whether byte ordering is bigendian... no
checking size of long long... 8
checking size of long int... 4
checking size of int... 4
checking size of short int... 2
checking size of long double... 16
checking size of double... 8
checking size of float... 4
checking size of char *... 4
checking for the null device... /dev/null
checking for gethostbyname... yes
checking whether mode_t is defined... yes
checking for availability of gettimeofday timing... yes
checking if gettimeofday needs timezone... yes
checking for availability of getrusage timing... yes
checking for availability of _ftime timing... no
checking for time.h... yes
checking for sys/time.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for string.h... yes
checking for assert.h... yes
checking for tgmath.h... yes
checking for sys/stat.h... yes
checking for getopt.h... yes
checking for dirent.h... yes
checking for c_asm.h... no
checking for intrinsics.h... no
checking for mach/mach_time.h... yes
checking for regex.h... yes
checking for sys/filio.h... yes
checking for sys/ioctl.h... yes
checking for sys/socket.h... yes
checking for netinet/in.h... yes
checking for netdb.h... yes
checking for arpa/inet.h... yes
checking for winsock2.h... no
checking for crypt.h... no
checking for signal.h... yes
checking for malloc.h... no
checking whether time.h and sys/time.h may both be included... yes
checking whether socklen_t is defined... yes
checking whether SOCKET is defined... no
checking for hrtime_t... no
checking for gethrtime... no
checking for read_real_time... no
checking for time_base_to_time... no
checking for clock_gettime... no
checking for mach_absolute_time... yes
checking for _rtc intrinsic... no
checking for mallinfo... no
checking for mallopt... no
checking whether M_MMAP_THRESHOLD is defined... no
checking if __int64 is defined... no
checking for vector... yes
checking for vector.h... yes
checking for getopt_long_only... yes
checking for working const... yes
checking for C inline... inline
checking for C restrict... __restrict__
checking for C++ restrict... __restrict__
checking for C bool... no
checking for CXX bool... yes
checking for Fortran REAL*4... yes
checking for Fortran REAL*8... yes
checking for Fortran REAL*16... yes
checking for Fortran COMPLEX*8... yes
checking for Fortran COMPLEX*16... yes
checking for Fortran COMPLEX*32... yes
checking for crypt... yes
checking for finite... yes
checking for isnan... yes
checking for isinf... yes
checking for mkstemp... yes
checking for va_copy... yes
creating cctk_Archdefs.h
creating make.arch.defn
creating cctk_Extradefs.h
creating make.extra.defn
cctk_Archdefs.h is unchanged
make.arch.defn is unchanged
cctk_Extradefs.h is unchanged
make.extra.defn is unchanged
updating cache ./config.cache
creating ./config.status
creating make.config.defn
creating make.config.deps
creating make.config.rules
creating cctk_Config.h
cctk_Config.h is unchanged
Determining number of fortran underscores...
Compiling test file with /Applications/Absoft10.1/bin/f77  ...
Lowercase - One trailing underscore
Compiling test file with /Applications/Absoft10.1/bin/f95  ...
Lowercase - No trailing underscore
________________________________________________________________________
Use make wavetoy to build the configuration.
________________________________________
From: users-bounces at cactuscode.org [users-bounces at cactuscode.org] On Behalf Of Erik Schnetter [schnetter at cct.lsu.edu]
Sent: Wednesday, May 14, 2008 4:07 PM
To: Cactus users mailing list
Subject: Re: [Users] problems with the Absoft compiler on Mac

Maria,

your configure output contains the steps that configure runs, but not
the results that configure finds.  Can you send the screen output
instead?

-erik

On May 14, 2008, at 14:26:29, Babiuc-Hamilton, Maria wrote:

> Hello Erik,
>
> Yes, you are right. That was silly from my part. I corrected it.
> However, the compilation is still stopped by the error:
>
> Checking status of thorn Boundary
> ________________________________________________________________________
> if [ ! -d ./ ] ; then mkdir -p ./ ; fi
> cd ./ ; make CCTK_TARGET=make.checked TOP=/Users/mariababiuc/Cactus/
> configs/wavetoy CONFIG=/Users/mariababiuc/Cactus/configs/wavetoy/
> config-data SRCDIR=/Users/mariababiuc/Cactus/arrangements/CactusBase/
> Boundary/src THORN=Boundary USESTHORNS="" -f /Users/mariababiuc/
> Cactus/lib/make/make.subdir
> make[3]: *** No rule to make target `ScalarBoundary.c.o', needed by
> `make.checked'.  Stop.
> make[2]: *** [make.checked] Error 2
> make[1]: *** [/Users/mariababiuc/Cactus/configs/wavetoy/lib/
> libthorn_Boundary.a] Error 2
>
> There are some error in the config.log file, which is attached. The
> problem seems to be with gcc. Would you please take a look?
>
> Thanks,
> Maria
> ________________________________________
> From: users-bounces at cactuscode.org [users-bounces at cactuscode.org] On
> Behalf Of Erik Schnetter [schnetter at cct.lsu.edu]
> Sent: Wednesday, May 14, 2008 1:11 PM
> To: Cactus users mailing list
> Subject: Re: [Users] problems with the Absoft compiler on Mac
>
> On May 14, 2008, at 08:59:30, Babiuc-Hamilton, Maria wrote:
>
>> Hello,
>>
>> I am trying to compile and run the wavetoy on a Mac laptop, with OSX
>> version 10.4.11 and Intel Core 2 Duo processor, and  Absoft10.1
>> fortran compiler, but I run into troubles.
>> The problem is:
>> ________________________________________________________________________
>> make[3]: *** No rule to make target `ScalarBoundary.c.o', needed by
>> `make.checked'.  Stop.
>> make[2]: *** [make.checked] Error 2
>>
>> I am using the config file that I found on the Cactus web page:
>>
>> CC=gcc
>> CXX=g++
>> F77=/Applications/Absoft10.1/bin/f77
>> F90=/Applications/Absoft10.1/bin/f95
>> -Dminimise_outstanding_communications=moc_toolong
>> -Duse_collective_communication_buffers=uccb_toolong
>
> Maria,
>
> you are receiving errors:
>
> Could not parse configuration line 5...
> '-Dminimise_outstanding_communications=moc_toolong'
> Could not parse configuration line 6...
> '-Duse_collective_communication_buffers=uccb_toolong'
>
> I believe that the two -D options should be on the same line as the
> F90 setting.
>
> -erik
>
> --
> Erik Schnetter <schnetter at cct.lsu.edu>   http://www.cct.lsu.edu/~eschnett/
>
> My email is as private as my paper mail.  I therefore support
> encrypting
> and signing email messages.  Get my PGP key from www.keyserver.net.
>
>
>
> <config.log>_______________________________________________
> Users mailing list
> Users at cactuscode.org
> http://www.cactuscode.org/mailman/listinfo/users


--
Erik Schnetter <schnetter at cct.lsu.edu>   http://www.cct.lsu.edu/~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.

More information about the Users mailing list