error MSB6006: “cmd.exe” exited with code 1

[UnlimitedChild]

Hello everyone,

I can not compile the project, because of an error "MSB6006: “cmd.exe” exited with code 1" I tried on 5 different computers, with 3 different Visual Studios (2013, 2015, 2017), there is always the same compilation error, what's wrong? Did someone have a similar compilation error? Can someone share a working project file for any visual studio, I would be very grateful for this help!

Thank you!

[dbabokin]

What ispc version are you using? Have you tried compiling examples?

…

Sent from my iPhone On Nov 25, 2017, at 9:27 AM, UnlimitedChild <notifications@github.com<mailto:notifications@github.com>> wrote: Hello everyone, I can not compile the project, because of an error "MSB6006: “cmd.exe” exited with code 1" I tried on 5 different computers, with 3 different Visual Studios (2013, 2015, 2017), there is always the same compilation error, what's wrong? Did someone have a similar compilation error? Can someone share a working project file for any visual studio, I would be very grateful for this help! Thank you! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#1304>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADWfGhPTeSYbcpq4ZbYCcKU5sSefe8Bsks5s6E4FgaJpZM4Qqfv6>.

[UnlimitedChild]

Latest release https://github.com/ispc/ispc/archive/v1.9.2.zip I tried to follow the documentation that came with the project. And then I started experimenting with msbuild, the result is always the same, I installed a new system and again got the same result. The parameters of libraries such as llvm, bison and other components do not affect this error. The language in Windows is always English.

[dbabokin]

Are you intentionally trying to build ispc yourself? The preferred way is to use pre-built binaries. I.e. https://sourceforge.net/projects/ispcmirror/files/v1.9.2/ispc-v1.9.2-windows.zip/download

The documentation for building ISPC on Windows is outdated (https://github.com/ispc/ispc/wiki/Building-ispc:-Windows) I need to update it. But it will mostly affect versions of different components (i.e. preferred LLVM is 5.0 currently).

[UnlimitedChild]

Hi dbabokin,

yees, Im trying to build a project on my own, because I would like to compile a debug version with the object files of each module. On what version of windows was the code compiled? In this case, as Ive already said, LLVM does not affect the build process at all, because this error occurs at an early stage of the build. I think the version of Windows somehow affects the error ...

[dbabokin]

I've developing in Windows Server 2008R2. But I don't think that this they key. Have you checked the logs to understand what command causes the crash? ISPC has quite many custom build commands. One of them should be a reason. Are you using GnuWin32?

[UnlimitedChild]

Im using msys and cygwin except for Visual Studio, here is the log that I get during the build, on Windows 7 the same.

1>------ Rebuild All started: Project: ispc, Configuration: Release Win32 ------
1> Building builtins.c
1> The system cannot find the path specified.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code 255.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

[dbabokin]

I have a bunch of logs in Release/ispc.tlog folder:
CL.command.1.tlog
CL.read.1.tlog
CL.write.1.tlog
custombuild.command.1.tlo
custombuild.read.1.tlog
custombuild.write.1.tlog
ispc.lastbuildstate
link.command.1.tlog
link.read.1.tlog
link.write.1.tlog

I think *command.1.tlog logs should give you a clue what's when wrong and how to reproduce.

[UnlimitedChild]

Thank you, it was necessary to look at the log file at once, I was 100% sure that I correctly wrote all the paths to the folders, although its clear that there is a problem with the paths. Ill try again.

custombuild.command.1.tlog.txt

[dbabokin]

This file looks good.
Just for the record, CL.command.1.tlog starts from ast.cpp and ends with parse.cc.
Release directory has 111 entries (110 files and ispc.tlog dir), including 48 *.obj files and 54 *.cpp files.

[UnlimitedChild]

How to add project additions correctly - m4, Flex, bison ?! I went through each stage of the installation with a triple check, stopped at the final stage, Cygwin is installed with these additions, both binary files and source codes. What features should I consider? Thank you for your help!

[dbabokin]

The recommended way to have all these is to install GnuWin32. I tried installing them though Cygwin, but it didn't work and I switched to GnuWin32. I haven't dug deeper. Wiki says the following: m4, flex (2.5 or later), and bison (2.4 or later). This didn't change.

Out of curiosity, why you are trying to make it work in this environment? If your goal to have a Windows build, you can just follow recommended way with GnuWin32. It's works pretty well. If you want Unix-style development on Windows - go with Win10 + docker (I've added docker files to the project recently).

[UnlimitedChild]

Hi,
I followed the old instructions on the site, I'll be happy to try with GnuWin32, I have the latest GnuWin32, what steps should I take to connect GnuWin32 correctly?

[dbabokin]

I think this is the important part from the build instructions (it's on LLVM configurations step) - but don't add it the path:

Set LLVM_LIT_TOOLS_DIR to point to your installation of GnuWin32 (typically C:/gnuwin32/bin)

[UnlimitedChild]

It's all done already, following the instructions https://github.com/ispc/ispc/wiki/Building-ispc%3A-Windows I stopped at

After LLVM has been installed, you can build ispc:
The following GNU tools must be installed (e.g. via cygwin) and in your PATH: m4, flex, and bison. Flex must be version 2.5 or later, and bison must be version 2.4 or later.
Set an environment variable, LLVM_INSTALL_DIR, that points to the directory in which you installed the LLVM headers, binaries, and libraries (e.g. C:/Users/yourname/llvm/bin-3.2).
Set an environment variable, LLVM_VERSION, with the value LLVM_3_2, or LLVM_3_3, or LLVM_3_4 depending on which version of LLVM you're using.
Launch a new instance of MSVC2010 and open the ispc.sln file.
Select the release x86 build, and build (F7)!
Your ispc executable will be in the Release/ directory of your ispc directory. Copy it to a directory in your PATH and you're ready to go.

[dbabokin]

Can you zip the log folder and share? Also run check_env.py and copy-paste it's output.

[UnlimitedChild]

check_env.py

=== in PATH: ===
Tools:
FIND ERROR: you don't have m4
FIND ERROR: you don't have bison
FIND ERROR: you don't have flex

SDE:
Warning: you don't have sde

ISPC:
Warning: you don't have ispc

C/C++ compilers:
Warning: you don't have clang
Warning: you don't have gcc
Warning: you don't have icc

=== in ISPC specific environment variables: ===
Warning: you have no LLVM_HOME
Warning: you have no ISPC_HOME
Warning: You have no SDE_HOME

ispc.tlog.zip