gfortran compiling problem,calling too many arguments


 
Thread Tools Search this Thread
Top Forums Programming gfortran compiling problem,calling too many arguments
# 1  
Old 01-16-2011
gfortran compiling problem,calling too many arguments

Hello,

My problem is with compiling a program modelling shallow water.

In it there is a subroutine called stat with 9 parameters.

In the main program it is called with 9 parameters also

I'm running Ubuntu 11.04 with gfortran version 4.5.

Thanks.

---------- Post updated at 11:57 PM ---------- Previous update was at 11:53 PM ----------

Oh and just to add the compiler output :
labshw.f:883.72:

call stat(npx,npy,grav,uinit,vinit,hinit,u,v,ho)
1
Error: Too many arguments in call to 'stat' at (1)

---------- Post updated 16-01-11 at 12:56 PM ---------- Previous update was 15-01-11 at 11:57 PM ----------

I solved the problem by installing Intel's free comipler Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

GFORTRAN library problem: libgFORTRAN.so.1 cannot open....

I've received some executable script for test, but executing this script continuously give me following message ./example: error while loading shared libraries: libgfortran.so.1: cannot open shared object file: No such file or directory Google search told me to do as following $... (1 Reply)
Discussion started by: exsonic
1 Replies

2. Shell Programming and Scripting

How to accept arguments in shell script when calling in perl

I have a shell script like this: #!/bin/sh $PYTHON MetarDecoder.py < ../data/mtrs/arg1/arg2 And I'm calling it with this in perl: my $output = `./metar_parse.sh --options`; It's successful when I put in actual values for arg1 and arg2 in the shell script, but I'd like to pass arguments... (1 Reply)
Discussion started by: civilsurfer
1 Replies

3. Programming

problem compiling with gfortran in two different debian releases

Hello, I hope this is the correct forum for this post. I have the following problem: A Fortran 77 program that has to deal with several large matrices (each approx. 5000 x 5000) and uses lapack and blas subroutines has been correctly compiled and executed using Debian Etch. When I tried... (1 Reply)
Discussion started by: currix
1 Replies

4. Programming

Compilation problem with gfortran

Hello everyone, I'm trying since a few days to compile a f90 program with gfortran (on Ubuntu) with a makefile. The fortran program calls 2 routines written in C. Here is my makefile: FC = gfortran SFC = gfortran FFLAGS = -ffree-form -O... (21 Replies)
Discussion started by: leroygr
21 Replies

5. Programming

gfortran compiling error: Expected a right parenthesis in expression at (1)

Hello, I am compiling a code with gfortran and get one error. I have not been successful in re-writing the line so that it will compile. Any suggestions for a re-written line? WRITE (IUNITITERV, 104) ((V(1,I),V(2,I)), I=1, NUMNOD) 1 Error:... (2 Replies)
Discussion started by: jm4smtddd
2 Replies

6. Shell Programming and Scripting

Calling a subroutine with arguments

Hello, I am having problem calling a subroutine with arguments, can any help? is the approach I am using correct? main() { # This is just a subset of the code #$b & $lnum is already define in this section of the code checkboard $b $lnum } checkboards() { ln=$lnum... (2 Replies)
Discussion started by: jermaine4ever
2 Replies

7. HP-UX

Problem in HP-UX compiling

Hi When im trying to do make --version and make --help in HP-UX it throws error Make: Unknown flag argument -. Stop. a soft link is present in this directory /usr/bin/make and hard link is in /usr/ccs/bin/make what could be the reason can any1 ..please tell me how to solve this... (1 Reply)
Discussion started by: vasanthan
1 Replies

8. Solaris

Problem in PowerDNS compiling

PowerDNS is true Power of Internet Name Management. http://www.powerdns.com Now, I compile it on my SunOS system (SunOS 5.8 Generic_117350-05 sun4u sparc SUNW,Ultra-5_10). ./configure -- no error make --> it has error: <i> make: Fatal error: Command failed for target... (0 Replies)
Discussion started by: secret4all
0 Replies

9. Solaris

Compiling problem

I'm trying to install the jed text editor on a SunOS 5.10 box. It depends on the s-lang library, which I installed to ~/lib. I'm trying to install jed to ~/jed (it's a box @ my university, so I don't have rights to install globally), but when I run make I get this error: It looks like it... (1 Reply)
Discussion started by: iandunn
1 Replies

10. Programming

Problem compiling metamail

Hi Guys. I have downloaded metamail from internet e Iīm trying to compile it at a SCO 5.0.5. In this server itīs working fine (letīs name it as mission1) iīm using the developer package in this server (mission1) and when I use mailto, i got the e-mail fine. Itīs forwarding to a exchange server... (2 Replies)
Discussion started by: ahnishimi
2 Replies
Login or Register to Ask a Question
ilaenv.f(3)							      LAPACK							       ilaenv.f(3)

NAME
ilaenv.f - SYNOPSIS
Functions/Subroutines INTEGER function ilaenv (ISPEC, NAME, OPTS, N1, N2, N3, N4) ILAENV Function/Subroutine Documentation INTEGER function ilaenv (integerISPEC, character*( * )NAME, character*( * )OPTS, integerN1, integerN2, integerN3, integerN4) ILAENV Purpose: ILAENV is called from the LAPACK routines to choose problem-dependent parameters for the local environment. See ISPEC for a description of the parameters. ILAENV returns an INTEGER if ILAENV >= 0: ILAENV returns the value of the parameter specified by ISPEC if ILAENV < 0: if ILAENV = -k, the k-th argument had an illegal value. This version provides a set of parameters which should give good, but not optimal, performance on many of the currently available computers. Users are encouraged to modify this subroutine to set the tuning parameters for their particular machine using the option and problem size information in the arguments. This routine will not function correctly if it is converted to all lower case. Converting it to all upper case is allowed. Parameters: ISPEC ISPEC is INTEGER Specifies the parameter to be returned as the value of ILAENV. = 1: the optimal blocksize; if this value is 1, an unblocked algorithm will give the best performance. = 2: the minimum block size for which the block routine should be used; if the usable block size is less than this value, an unblocked routine should be used. = 3: the crossover point (in a block routine, for N less than this value, an unblocked routine should be used) = 4: the number of shifts, used in the nonsymmetric eigenvalue routines (DEPRECATED) = 5: the minimum column dimension for blocking to be used; rectangular blocks must have dimension at least k by m, where k is given by ILAENV(2,...) and m by ILAENV(5,...) = 6: the crossover point for the SVD (when reducing an m by n matrix to bidiagonal form, if max(m,n)/min(m,n) exceeds this value, a QR factorization is used first to reduce the matrix to a triangular form.) = 7: the number of processors = 8: the crossover point for the multishift QR method for nonsymmetric eigenvalue problems (DEPRECATED) = 9: maximum size of the subproblems at the bottom of the computation tree in the divide-and-conquer algorithm (used by xGELSD and xGESDD) =10: ieee NaN arithmetic can be trusted not to trap =11: infinity arithmetic can be trusted not to trap 12 <= ISPEC <= 16: xHSEQR or one of its subroutines, see IPARMQ for detailed explanation NAME NAME is CHARACTER*(*) The name of the calling subroutine, in either upper case or lower case. OPTS OPTS is CHARACTER*(*) The character options to the subroutine NAME, concatenated into a single character string. For example, UPLO = 'U', TRANS = 'T', and DIAG = 'N' for a triangular routine would be specified as OPTS = 'UTN'. N1 N1 is INTEGER N2 N2 is INTEGER N3 N3 is INTEGER N4 N4 is INTEGER Problem dimensions for the subroutine NAME; these may not all be required. Author: Univ. of Tennessee Univ. of California Berkeley Univ. of Colorado Denver NAG Ltd. Date: November 2011 Further Details: The following conventions have been used when calling ILAENV from the LAPACK routines: 1) OPTS is a concatenation of all of the character options to subroutine NAME, in the same order that they appear in the argument list for NAME, even if they are not used in determining the value of the parameter specified by ISPEC. 2) The problem dimensions N1, N2, N3, N4 are specified in the order that they appear in the argument list for NAME. N1 is used first, N2 second, and so on, and unused problem dimensions are passed a value of -1. 3) The parameter value returned by ILAENV is checked for validity in the calling subroutine. For example, ILAENV is used to retrieve the optimal blocksize for STRTRI as follows: NB = ILAENV( 1, 'STRTRI', UPLO // DIAG, N, -1, -1, -1 ) IF( NB.LE.1 ) NB = MAX( 1, N ) Definition at line 163 of file ilaenv.f. Author Generated automatically by Doxygen for LAPACK from the source code. Version 3.4.1 Sun May 26 2013 ilaenv.f(3)