I installed new Windows 10, Visual Studio 2015, Visual C++ 2008 for Python 2.7, Miniconda 2, Miktex, Iron Python 2.7.5 and everything is in PATH in env variables.
In normal CMD.exe I can do:
C:\Users\robgr>pdflatex
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9 64-bit)
**
C:\Users\robgr>ipy64
IronPython 2.7.5 (2.7.5.0) on .NET 4.0.30319.42000 (64-bit)
Type "help", "copyright", "credits" or "license" for more information.
>>> ^Z
C:\Users\robgr>conda
usage: conda-script.py [-h] [-V] [--debug] command ...
conda is a tool for managing and deploying applications, environments and packages.
But in Visual C++ 2008 64-bit Command Prompt I got:
Setting environment for using Microsoft Visual Studio 2008 x64 tools.
C:\Users\robgr\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Visual C++ Compiler Package for Python 2.7>pdflatex
'pdflatex' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\robgr\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Visual C++ Compiler Package for Python 2.7>ipy64
'ipy64' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\robgr\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Visual C++ Compiler Package for Python 2.7>conda
usage: conda-script.py [-h] [-V] [--debug] command ...
But before everythin worked fine...
What may be the problem here?
EDIT:
"Visual C++ 2008 64-bit Command Prompt" has command : C:\Windows\SysWOW64\cmd.exe /k ""C:\Users\robgr\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\vcvarsall.bat" amd64"
Path to "conda" : Q:\Python\Miniconda2\Scripts\conda.exe
Path to conda Python env "python27a" : Q:\Python\Miniconda2\envs\python27a
Path to IronPython "ipy64" : Q:\Python\IronPython\ipy64.exe
Path to "pdflatex" : Q:\LaTex\MiKTeX\v2.9\miktex\bin\x64\pdflatex.exe
PATH in global envs:
T:\Microsoft\Solver Foundation\3.0.2.10889\Plugins;
C:\Program Files\Haskell\bin;
Q:\Haskel\7.10.2-a\lib\extralibs\bin;
Q:\Haskel\7.10.2-a\bin;
Q:\Python\Miniconda2\envs\python27a\Lib\site-packages\PyQt4;
Q:\Haskel\2014.2.0.0\lib\extralibs\bin;
Q:\Haskel\2014.2.0.0\bin;
C:\ProgramData\Oracle\Java\javapath;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm;
C:\Program Files\Microsoft SQL Server\130\Tools\Binn;
Q:\C\PCL\v1.6.0\bin;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft SQL Server\120\Tools\Binn;
C:\Program Files (x86)\nodejs;
Q:\Haskel\2014.2.0.0\mingw\bin;
Q:\Haskel\7.10.2-a\mingw\bin;
Q:\Python\Miniconda2;
Q:\Python\Miniconda2\Scripts;
Q:\Python\Miniconda2\Library\bin;
D:\Internet\WinSCP\WinSCP;
c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit;
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5;
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5\Doctrine extensions for PHP;
U:\MATLAB\R2015a\runtime\win64;
U:\MATLAB\R2015a\bin;
U:\MATLAB\R2015a\polyspace\bin;
C:\Program Files\Hewlett-Packard\SimplePass;
Q:\Python\IronPython;
Q:\Python\IronPython\ipy64.exe;
Q:\LaTex\MiKTeX\v2.9\miktex\bin\x64;
D:\System\Git\cmd`
PATH seen in vcpp 2008 cmd:
C:\Users\robgr\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Visual C++ Compiler Package for Python 2.7>echo %PATH%
C:\Users\robgr\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\x86_amd64;
C:\Users\robgr\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\WinSDK\Bin;
T:\Microsoft\Solver Foundation\3.0.2.10889\Plugins;
C:\Program Files\Haskell\bin;
Q:\Haskel\7.10.2-a\lib\extralibs\bin;
Q:\Haskel\7.10.2-a\bin;
Q:\Python\Miniconda2\envs\python27a\Lib\site-packages\PyQt4;
Q:\Haskel\2014.2.0.0\lib\extralibs\bin;
Q:\Haskel\2014.2.0.0\bin;
C:\ProgramData\Oracle\Java\javapath;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm;
C:\Program Files\Microsoft SQL Server\130\Tools\Binn;
Q:\C\PCL\v1.6.0\bin;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft SQL Server\120\Tools\Binn;
C:\Program Files (x86)\nodejs;
Q:\Haskel\2014.2.0.0\mingw\bin;
Q:\Haskel\7.10.2-a\mingw\bin;
Q:\Python\Miniconda2;
Q:\Python\Miniconda2\Scripts;
Q:\Python\Miniconda2\Library\bin;
D:\Internet\WinSCP\WinSCP;
c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit;
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4
PATH seen in normal cmd:
C:\Users\robgr>echo %PATH%
T:\Microsoft\Solver Foundation\3.0.2.10889\Plugins;
C:\Program Files\Haskell\bin;
Q:\Haskel\7.10.2-a\lib\extralibs\bin;
Q:\Haskel\7.10.2-a\bin;
Q:\Python\Miniconda2\envs\python27a\Lib\site-packages\PyQt4;
Q:\Haskel\2014.2.0.0\lib\extralibs\bin;
Q:\Haskel\2014.2.0.0\bin;
C:\ProgramData\Oracle\Java\javapath;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm;
C:\Program Files\Microsoft SQL Server\130\Tools\Binn;
Q:\C\PCL\v1.6.0\bin;
C:\Users\robgr\.dnx\bin;
C:\Program Files\Microsoft SQL Server\120\Tools\Binn;
C:\Program Files (x86)\nodejs;
Q:\Haskel\2014.2.0.0\mingw\bin;
Q:\Haskel\7.10.2-a\mingw\bin;
Q:\Python\Miniconda2;
Q:\Python\Miniconda2\Scripts;
Q:\Python\Miniconda2\Library\bin;
D:\Internet\WinSCP\WinSCP;
c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit;
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4
Hehe -.- MySQL was bugging in PATH:
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5
c:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5\Doctrine extensions for PHP
And when I opened vcpp 2008 cmd there was...
Setting environment for using Microsoft Visual Studio 2008 x64 cross tools.
'MySQL' is not recognized as an internal or external command,
operable program or batch file.
'MySQL' is not recognized as an internal or external command,
operable program or batch file.
But this part "'MySQL' is not recognized " I was neglecting as non important (in previous windows was at end in PATH), so I was removing it from question in this post... But the this is that this sign "&" if included in PATH is acting as separate command. So this was making bug.
When I remove this sign "&" from PATH or path containing this "&" its working now :)
Related
I'm searching for the latest version of sign tool. Already installed latest windows 10 SDK, but signtool.exe date did not change.
Starting from windows 10 SDK, the signtool.exe is now located here:
C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x64
In this example, I used the Windows 10 Fall Creators Update SDK-Version (10.0.16299) - and 64bit edition
Be careful, additionally it may be located here: C:\Program Files (x86)\Windows Kits\10\App Certification Kit
Update: Windows 10 Build 1809, now here C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64
Update: Visual Studio 2022: C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64
If I do not install Windows 10 SDK, but install Visual Studio, I typically find signtool.exe in the following location:
C:\Program Files (x86)\Microsoft SDKs\ClickOnce\SignTool\signtool.exe
This is a constant path that doesn't depend on the version of the Windows SDK. It's very convenient to use it in bat files or another automation stuff.
If you install the 'Windows 10 SDK' ( https://developer.microsoft.com/en-gb/windows/downloads/windows-10-sdk/ ) then it'll be at C:\Program Files (x86)\Windows Kits\10\bin\x64 as somewhere static that won't change.
What am I missing below (path, environment variable, ?) running from a Windows Command Prompt window.
See “gdb-7.12\configure' is not recognized as an internal or external command, operable program or batch file.” below:
C:\Users\_gerlad0_\Downloads\Installables\gdb-7.12\build>C:\Users\_gerlad0_\Downloads\Installables\gdb-7.12\configure
'C:\Users\_gerlad0_\Downloads\Installables\gdb-7.12\configure' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\_gerlad0_\Downloads\Installables\gdb-7.12\build>set path
Path=C:\Program Files (x86)\GNU Tools ARM Embedded\5.4 2016q2\bin\;C:\ProgramData\Oracle\Java\javapath;
C:\Program Files\Common Files\Microsoft Shared\Windows Live;
C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;
C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;
C:\Program Files\Wave Systems Corp\Gemalto\Access Client\v5\;C:\Program Files (x86)\Windows Live\Shared;
c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\TortoiseSVN\bin;
C:\Program Files (x86)\QuickTime\QTSystem\;
C:\Program Files (x86)\Skype\Phone\;C:\WINDOWS\system32\config\systemprofile.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;
C:\Program Files\Git\cmd;C:\cygwin64\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Thanks for any insight!!
Most configure scripts are written for the unix shell(s).
You need to run configure from such unix shell (bash for example), which you should get from cygwin/mingw/msys package for your windows.
I have
ActivePerl 5.24 x86
NASM 2.12.02
Visual Studio 2010 Ultimate 10.0.30309
Windows 7 Ultimate x64
I extracted source code, opened Visual Studio Command Prompt (2010) and entered following command:
perl Configure VC-WIN32 --prefix:C:\openSSL-win32
I get this error:
It looks like you don't have either nmake.exe or dmake.exe on your
PATH, so you will not be able to execute the commands from a Makefile.
You can install dmake.exe with the Perl Package Manager by running:
ppm install dmake
I surely have nmake in VS Command Prompt. How can I tell Perl to see my nmake in VS directory?
P.S. These paths are my in my %PATH%:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin
C:\Perl\bin
C:\Program Files (x86)\NASM
EDIT: Below is my current PATHs.
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\
C:\Perl\site\bin
C:\Perl\bin
C:\app\User\product\11.2.0\client_1\bin
C:\ProgramData\Oracle\Java\javapath
C:\Program Files (x86)\Intel\iCLS Client\
C:\Program Files\Intel\iCLS Client\
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Program Files\Intel\WiFi\bin\
C:\Program Files\Common Files\Intel\WirelessCommon\
C:\Program Files\ThinkPad\Bluetooth Software\
C:\Program Files\ThinkPad\Bluetooth Software\syswow64
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
C:\SWTOOLS\ReadyApps
C:\Program Files (x86)\Common Files\Lenovo
c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\
c:\Program Files\Microsoft SQL Server\100\Tools\Binn\
c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
C:\Program Files\Microsoft\Web Platform Installer\
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\
C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\
C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\
C:\Program Files (x86)\NASM\
Here is how I solved it (actually openssl's developers in github helped me). I installed Strawberry Perl, installed Visual Studio 2010 SP1 (free to download, about 1.5 GB, you can download ISO format too in Install Instructions section, this is necessary), installed Windows 7 SDK 7.1 (maybe isn't necessary, if nothing worked install it), istalled NASM. Opened Visual Studio 2010 Command Prompt (shortcut is in start menu). Go to the folder that openSSL source code exists in VS Command Prompt. Then input these commands:
perl Configure VC-WIN32
nmake
nmake test
nmake install
After nmake test you should see STATUS: PASSED. After nmake install check your Program Files (x86) folder. There should be two DLLs and openssl.exe.
P.S. put NASM and Perl in your %PATH%.
Good luck
I have Installed Windows SDK on windows 10 from here
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
But I am unable to open Windows SDK command prompt to run my maven commands to install hadoop. I have searched online but didn't find anything useful. Please help.
The Windows 7.1 SDK was really the last one to include it's own "Command Prompt". For Windows 8.x and Windows 10 SDK, you usually install Visual Studio to get the Windows SDK which provides the "Developer Command Prompt" shortcut.
Keep in mind that the Windows 10 SDK uses a "side-by-side" model so C:\Program Files (x86)\Windows Kits\10\Include or Lib\<arch> is not sufficient to point to the include/lib path. You need to add a version string. For example, for the November 2015 update, it would be C:\Program Files (x86)\Windows Kits\10\Include\10.0.10586.0 and C:\Program Files (x86)\Windows Kits\10\Lib\10.0.10586.0\um\<arch>
In the Visual Studio 2015 Developer Command Prompt, you will see the following environment variables:
WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\
WindowsSDKLibVersion=10.0.10586.0\
WindowsSDKVersion=10.0.10586.0\
INCLUDE=...C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\ucrt;
C:\Program Files (x86)\Windows Kit s\NETFXSDK\4.6.1\include\um;
C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\shared;
C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\um;
C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\winrt;
LIB=...C:\Program Files (x86)\Windows Kits\10\lib\10.0.10586.0\ucrt\x64;
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64;
C:\Program Files (x86)\Windows Kits\10\lib\10.0.10586.0\um\x64;
LIBPATH=...C:\Program Files (x86)\Windows Kits\10\UnionMetadata;
C:\Program Files (x86)\Windows Kits\10\References;
C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.VCLibs\14.0\References\CommonConfiguration\neutral;
I've installed MinGW-builds and the 64-bit version of MinGW.
When I try to run the Run Terminal program from the install, I get the following output:
C:\Program Files\mingw-builds\x64-4.8.1-posix-seh-rev4>echo off
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>
I cannot execute make and other commands that come with the installation, so it seems like I've somehow reverted to the basic Windows cmd terminal.
How can I identify why MinGW terminal is missing functionality?
I have previously installed MinGW using the package manager, as well as MSYS. I've removed them as best I can, and used CCleaner to clean up references to them.
I checked my PATH but I cannot see obvious issues:
C:\Program Files\mingw-builds\x64-4.8.1-posix-seh-rev4\mingw64\bin;
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
%CommonProgramFiles%\Microsoft Shared\Windows Live;
C:\Program Files (x86)\AMD APP\bin\x86_64;
C:\Program Files (x86)\AMD APP\bin\x86;
C:\Program Files (x86)\RSA SecurID Token Common;
C:\Program Files\Java\jdk1.7.0_05\bin;
C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;
C:\Users\James\Desktop\bpmndev\apache-maven-3.0.5\bin;
C:\Windows\System32;
C:\Go\bin;
C:\Program Files (x86)\scala\\bin;
C:\Program Files (x86)\CMake 2.8\bin;
C:\Program Files\Common Files\Microsoft Shared\Windows Live
Try install MSYS again. It works with MinGW-w64 (actually it should work with any MinGW version). Just open the MSYS terminal, configure with options like "--build=x86_64-w64-mingw32" and make.