- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
in a old fixed format f77 routine, is it possible to use "USE" statement? I have a old routine, and a module just to pass name of directories:
in a f77 routine atompp as
ATOM/atompp.o: In function `atompp_':
ATOM/atompp.f:(.text+0x318): undefined reference to `parameters_mp_asr_dir_'
so whats wrong with this?
[cpp]module parameters
character(25)::ASR_DIR='/home/rudra/Recursion/ASR/'
character(28)::LMA_DIR='/home/rudra/Recursion/LMTO_A/'
character(28)::LMB_DIR='/home/rudra/Recursion/LMTO_B/'
end module parameters
[/cpp]
in a f77 routine atompp as
[cpp]subroutine atompp(avw,clabl,kap2,lfree,lmx,lrel,nclass,nl,nsp,pp,
. sigma,ves,vmtz,wsr,z)
use parameters
...[/cpp]
while compiling, i am getting error,ATOM/atompp.o: In function `atompp_':
ATOM/atompp.f:(.text+0x318): undefined reference to `parameters_mp_asr_dir_'
so whats wrong with this?
링크가 복사됨
4 응답
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
There's nothing wrong with the USE. The problem is that when linking, you have to supply the .o that resulted from compiling module "parameters".
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Quoting - Steve Lionel (Intel)
There's nothing wrong with the USE. The problem is that when linking, you have to supply the .o that resulted from compiling module "parameters".
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
When you say f90-f77 mismatch, are you using two different compilers or are you applying the "f77" term to fixed-form source compiled with ifort? If two different compilers, that's not supported. If it's a mixture of fixed-form and free-form, that doesn't matter.
Perhaps using nm to examine the symbols in the .o would be enlightening, looking to see if anything similar to the missing symbol is defined.
Perhaps using nm to examine the symbols in the .o would be enlightening, looking to see if anything similar to the missing symbol is defined.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Quoting - Steve Lionel (Intel)
Perhaps using nm to examine the symbols in the .o would be enlightening, looking to see if anything similar to the missing symbol is defined.
how can i check .o files? this in not human readable...iam in linux