- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hey folks !
I have a working project on Compaq visual fortran (written a couple years back now), but I'd like to migrate it to IVF to work on it.
Problem, I have a few compatibility problems I would need help on.
First thing first, this annoying error 6796 on pointers
R:\r.egal\Projets en cours\Programmes\Prosec3D\Test Intel\Prosec3D\Source1.f90(6): error #6796: The variable must have the TARGET attribute or be a subobject of an object with the TARGET attribute, or it must have the POINTER attribute. [MAILLE]
The corresponding code (simplified) would be
subroutine case_x(maille) integer, intent(inout) :: maille integer, pointer :: pt_P !----------------------------------- nullify(pt_P) pt_P=>maille end subroutine case_x
Why do I have this error when it works just fine in older versions ?
Is there an option in the project properties I'd have to check ?
Please advise
Cheers
Renaud
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
From the link the OP posted, it seemed possible that installation of NVIDIA drivers may have corrupted the PATH environmental variable. It seemed to me possible that a clean install might fix such corruption without much effort.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Steve Lionel (Intel) wrote:
I'm sorry that you're having these problems - could we perhaps arrange for me to connect to your system and have a look to see what is happening? If this is acceptable, I'll send you email and arrange a time for this.
Sure, we could do that ;)
But it seems that NVidia modifies dynamically the path value, so that appears in fortran build log. The link says that indeed NV could be the problem adding dumb "." or useless ";".
I'll look into reinstalling the drivers, but since I am not really the administrator of my computer-IT department- (I have admin rights though), that's quite complicated to go that far. The model of my graphic card is exactly the same as the one mentioned in the link above. That's why I thought it would be relevant.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I had not clicked on your link before - wow - I would never have guessed that the Nvidia Optimus technology would create this problem. It does seem as if a later driver might fix it and you should ask your administrator to update the driver and see if that resolves the issue.
