1836283 Members
1723 Online
110097 Solutions
New Discussion

Re: compiling error

 
lou_jun21
Occasional Contributor

compiling error

when i type command.
$ ./configure --prefix=/nfs/dkr2/users/jjlou/install LDFLAGS=L/opt/fortran/lib

error is observed in config.log

## ------------ ##
## Core tests. ##
## ------------ ##

configure:945: PATH=".;."; conftest.sh
./configure[946]: conftest.sh: not found.
configure:948: $? = 127
configure:961: checking for vendor f77 to be used instead of g77
configure:963: result:
configure:969: checking for f77
configure:984: found /opt/fortran/bin/f77
configure:992: result: f77
configure:1087: checking for Fortran 77 compiler version
configure:1090: f77 --version &5
f77: Option not recognized: --
f77: Option not recognized: -e
f77: Option not recognized: -r
f77: Option not recognized: -i
LPATH is : /opt/fortran/lib/pa1.1:/usr/lib/pa1.1:/opt/fortran/lib:/usr/lib:/opt/langtools/lib
configure:1093: $? = 0
configure:1095: f77 -v &5
LPATH is : /opt/fortran/lib/pa1.1:/usr/lib/pa1.1:/opt/fortran/lib:/usr/lib:/opt/langtools/lib
configure:1098: $? = 0
configure:1100: f77 -V &5
configure:1103: $? = 0
configure:1116: checking for Fortran 77 compiler default output
configure:1119: f77 L/opt/fortran/lib conftest.f >&5
f77: Cannot read file L/opt/fortran/lib
f77: Errors detected, no link
configure:1122: $? = 1
configure: failed program was:
program main

end
configure:1145: error: Fortran 77 compiler cannot create executables


2 REPLIES 2
Steven Sim Kok Leong
Honored Contributor

Re: compiling error

Hi,

>> configure:945: PATH=".;."; conftest.sh
>> ./configure[946]: conftest.sh: not found.

Notice that your PATH variable only contains your current directory.

Can you find a conftest.sh? From your compilation directory, run this:

# find ./ -name conftest.sh

Hope this helps. Regards.

Steven Sim Kok Leong
Deepak Extross
Honored Contributor

Re: compiling error

Looks like someone has deleted or moved the file conftest.sh from your current directory.

Try to get a copy of this file into your current directory and then re-run your command.