Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor I
488 Views

Input line too long error when running Windows batch file

When running an IVF project through a Windows batch file through a regular command prompt i.e. not the one provided by the Intel compiler, an error periodically shows up with the message "Input line too long". Is this Windows or IVF related? 

The batch files always begin by setting the correct environment ex.

call "%IFORT_COMPILER19%bin\ipsxe-comp-vars.bat" ia32 vs2017

Some characteristics of the error (when it appears) are:

1. Occurs when the batch file is repeatedly executed in the same command window.

2. Disappears when the command window is closed and restarted.

3. Could the repeated call to the ipsxe-comp-vars.bat be the problem?

0 Kudos
2 Replies
Highlighted
Valued Contributor II
488 Views

I suspect that it is indeed the repeated call that causes this. Typically such batch files as ipsxe-comp-vars.bat prepend or append all manner of paths to the existing PATH variable. At some point it is simply too much.

You could try with:

setlocal

... contents of your current batch file

endlocal

This confines the effects of enhancing the PATH variable (and other variables) to the period that the batch file is active. Under Linux shells each process (shell scripts or whatever) can only influence its own copy of the environment, but that is not automatically the case with Windows command shells/DOS boxes.

0 Kudos
Highlighted
Beginner
488 Views

You can try LongPathTool to fix this problem. It worked perfectly for me.

0 Kudos