- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Might sound stupid, but I don't know what to do when I'm on command line prompt. I'm not a programmer at all, so I'm kind of relying on the automatic compilation of IDE until now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you use the VS2010 Shell, additional Microsoft tools and libraries are installed in a folder under Program Files (x86)\Microsoft Visual Studio 10.0. There will be an Intel Fortran folder under that, and then some other folders. Look there to find the folder with link.exe. Copy that complete folder path. Go to the place you found the "Executables" folder list you pasted above. Add to this list the folder you found with link.exe., then try the build again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
based on the link I mentioned earlier, I already did that. I took the directory (see image below), and added it to executables list. That's when I get the error 10037
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please do this, In Visual Studio, select Tools > Options. I think in version 14 the next level I want is Intel Composer XE (in 15.0 it is Intel Compilers and Tools.) Then Visual Fortran > General. Under Build Options, change "Show environment in log" to True and click OK. Now do a build again. Attach a zip of the buildlog.htm from the Debug or Release folder to a reply here so I can look at it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning,
since I did not receive any further answer to my problem, I suppose that I described a problem that has either a trivial solution, either no one has ever encountered this before.
In both cases, I'm still stuck with it. Please help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, missed this over the Thanksgiving holiday. Does the folder
c:\Program Files (x86)\Microsoft Visual Studio 10.0\Intel Fortran\Microsoft Files\VC\BIN
exist and is there a LINK.EXE in it? The other warnings you get during the build suggest to me that the Visual Studio Shell didn't get correctly installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Steve,
yes this folder does exist, and does also contain the executable file IVF's looking for (among others, see attached file)
I understand that the installation must have been corrupted, should I reinstall or something ? I'm just so scared that I can not succeed in making it work again afterwards. Is there an alternative you can think of ?
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think an uninstall and reinstall would be good to try. In addition to uninstalling Fortran, also uninstall:
Microsoft Visual Studio 2010 Shell (Integrated) - ENU
Microsoft Visual Studio 2010 Files for Intel Visual Fortran
Microsoft Visual Studio 2010 Remote Debugger – ENU
Delete the Microsoft Visual Studio 10.0 folder before reinstalling.
An alternative is to install the VS2013 Community Edition (if you qualify for the license terms), then install Fortran.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After the reinstall, if you chose to reinstall the VS2010 Shell, install Visual Studio 2010 Service Pack 1 from Microsoft.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
I understand that's probably the best solution.
I will try it but I don't really know what are the software I am looking for in this uninstall/reinstall
OK for all microsoft visual studio features you listed above. What about uninstalling "Fortran". Where is that ? Would that be "C:\Program Files (x86)\Intel" and all types of Composer XE here ?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You do the uninstalls from Control Panel > Programs and Features. Don't just delete files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't risk doing it right now, since I have no idea how works the licencing system.
I'll do it when my project is on a stable version.
Still, I'd like to know what you mean by "uninstall Fortran". I do not have such a "program" installed in my control panel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok - it now appears as "Intel Parallel Studio XE 2015 Composer Edition. There will be no effect on licensing.
As an alternative, install VS2013 Community Edition and, instead of uninstalling Fortran (Parallel Studio XE 2015), do a Change/Modify and select the option to integrate with VS2013, then use that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
I'm so sad right now !
I uninstalled all previous VS products (8, 10) and previous Intel Composer XE. Then I downloaded and installed VS2013 Community as you suggested. Then I reinstalled the compiler and tried to compile.
The buildlog attached shows same problem as before, I think : link.exe can't be found
I found it in "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin", I don't understand.
edit : anyway, I can see that this VS2013 product is not free, and I don't think I have a licence for that. So that's not the solution I'm looking for. I just spend one day installing VS2013 and I have to go back -.-
So, is there a way to install my old VS2010shell ? Does that require a licence ? If yes how can I retrieve my old one ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The VS2013 Community Edition is free.
Looking at the definition of PATH I see something odd:
C:\Windows\system32\NV;.;;
It's REALLY a bad idea to have "." in PATH as this can open you up to all sorts of security issues. I'm not sure if the ;; is also a problem.
- Right click on Computer (on your desktop) and select Properties. Click on "Advanced system settings" in the left column.
- Click on the Advanced tab if not already selected and then Environment Variables.
- You will see two lists, one for the user and one for the system. Find "path" (or "PATH") in each and click Edit.
- Find and remove ";.;" where it appears, then click OK, OK, OK.
- Restart Visual Studio and try your build again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
yes it is odd indeed, because when I look at environment variables, they look just fine. I can't find neither this ";.;;", nor system32\NV for that matter. I googled it and it seems that comes from graphic card switch, and I'm really not ready to unable some features in the BIOS. I am not a computer specialit, and I've got no authority to modify this anyway.
So I guess I'll stay with my VS2010 shell and compiler 12 since I do not experiment problems with this configuration.
Thanks a lot for the help anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oooh, NVIDIA driver problems! I just got a new TV and I couldn't make it work with my new computer. Everything else, including my old computer, worked on my new TV, and my new computer could connect with my old TV and a VGA monitor simultaneously, but new TV+new computer = .FALSE. It turned out that drivers were the culprit. My new TV is supposed to be able to download new software on demand, but that feature doesn't actually work, so the only way to upgrade the firmware is to plug the ethernet cable into it, turn it off, and go to sleep so it can do the auto update overnight.
That didn't fix the problem, though, so I turned to the NVIDIA driver. They have a thing call GeForce Experience which is supposed to automatically check for driver updates and install them, but it turned out that it thought that my driver was up to date when it was version 344.11 and the latest version was 344.75. So I went to NVIDIA's website and installed the drivers myself and selected a custom install so I could request a clean install. After that my new TV+new computer worked. I don't know whether it was the new driver or just the clean install, but maybe you could try updating your driver on NVIDIA's web page and doing a clean install as well. That might fix up some of the junk that their old installation programs could have left behind.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Repeat Offender wrote:
Oooh, NVIDIA driver problems! ..
Wrong forum (!), or does Dr Fortran help with these too?! :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The NV folder in PATH was just before the ., so I mentioned it only to help find it. I doubt it has any relevance. I have an NVidia card in my work computer and my home PC as well. No interference with Fortran.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page