Problem with long/special routes and output list of errors?

[Daniel_Dopico]

I moved from Intel 2022 to 2025 and I am experiencing problems with the Output list of errors. Before I could double click on each error and Visual Studio automatically takes you to the line where the error is. Since I updated, the environment is unable to link the errors to the code. 

I checked with both Visual Studio Community 2017 and 2022 and my guess is that the new compiler is having trouble with long routes or special characters. I have the code in a long route with spaces and some special characters like "ñ". If I move the code to a shorter route it seems that it works.

Are you aware of this problem?

[jimdempseyatthecove]

You have two windows showing the errors: Errors and Output

If you are having issues with clicking on an error in the Errors window, try clicking on it in the Output Window.

BTW, the Errors window should work.

Jim Dempsey

[Daniel_Dopico]

Thank you Jim.

I tried both. None of them work.

I would say that BOTH should work since they have been working with that code and routes for years, but none of them does. 

Is it possible to be something related to Intel 2025?

[jimdempseyatthecove]

I do not have any issues with locating the error position in the source code.

ifort from 2024.2

ifx from 2025.0.0

MS VS Community 2022 V17.8.2

Jim Dempsey

[andrew_4619]

Ditto but VS 17.0.5, no issues with ifort/ifx

[Daniel_Dopico]

Maybe you are not aware, but I think that the problem exists:

If I use the original route "C:\Users\user\OneDrive - Company da Coruña" it doesn't work.

It I create a virtual drive: subst O: "C:\Users\user\OneDrive - Company da Coruña" it works.

I don't know if the problem is the "ñ" character or any other but something that was working during years, stopped working for me.