Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RAVEN Build Error on Windows #1241

Closed
10 tasks done
KwesiBoafo opened this issue May 23, 2020 · 18 comments
Closed
10 tasks done

RAVEN Build Error on Windows #1241

KwesiBoafo opened this issue May 23, 2020 · 18 comments

Comments

@KwesiBoafo
Copy link

KwesiBoafo commented May 23, 2020


Defect Description

I tried to install the windows version of RAVEN and upon attempting to build raven, I get the following error message:
"error: Error executing cmd /u /c "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64 && set"

I have attempted several ways to get it to work but to no avail. Kindly provide guidance on how to address this error.

Describe the defect

What did you expect to see happen?

For RAVEN to build successfully

What did you see instead?

An error message as described above.

Do you have a suggested fix for the development team?

None

Describe how to Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.

Screenshots and Input Files
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.
image

Platform (please complete the following information):

  • OS: [e.g. iOS] Windows
  • Version: [e.g. 22]
  • Dependencies Installation: [CONDA or PIP] Conda

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@tyler477
Copy link

I have a similar issue, currently. Did you ever end up fixing the issue? If so, could you kindly give some insight? Much appreciated!

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

Hi @tyler477 and @KwesiBoafo . It looks like that we missed this issue and we deeply apologize.

Are you still experiencing this problem? If so (@tyler477 since you just commented on this issue), can you attach your error?
In addition, are you using the CMD or the GitBash terminal? If you are using the CMD, can you try in GitBash directly?
Thank you

@tyler477
Copy link

tyler477 commented Oct 27, 2020

@alfoa, Thanks so so much for a quick response!

Yes, I am still experiencing the issue (attached screenshot below). I am using the CMD on windows 10. I will try momentarily on GitBash directly.

CMD

edit: I just tried on GitBash directly and it appears to give this exact result.

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

Okay. Thank you. Let me check in my remote win machine.
In the meanwhile, (sorry in advance for the silly question). Did the Visual Studio installation go through (at least "Desktop development with C++")
Andrea

@tyler477
Copy link

Yes. I have Visual Studio installed and working on my desktop with the C++ extension

Tyler

@KwesiBoafo
Copy link
Author

KwesiBoafo commented Oct 27, 2020 via email

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

@tyler477 can I ask you to print and paste your path here (in GitBash):

echo $PATH

In addition, which version of Visual Studio are you using?

@KwesiBoafo I am really sorry. We really missed this issue. I hope you can give another try once this issue is solved.

@tyler477
Copy link

@alfoa I am using visual studio version 1.43.2

After printing my path, it returned:

/c/Users/Tyler/bin:/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/mingw64/bin:/usr/bin:/c/Users/Tyler/bin:/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/WINDOWS/System32/WindowsPowerShell/v1.0:/c/WINDOWS/System32/OpenSSH:/c/Program Files/MATLAB/R2020b/runtime/win64:/c/Program Files/MATLAB/R2020b/bin:/c/Program Files/MATLAB/R2018b/bin:/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/110/Tools/Binn:/c/Program Files (x86)/Microsoft SQL Server/120/Tools/Binn:/c/Program Files/Microsoft SQL Server/120/Tools/Binn:/c/Program Files/Microsoft SQL Server/120/DTS/Binn:/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/cmd:/mingw64/bin:/usr/bin:/c/Program Files/PuTTY:/c/Users/Tyler/miniconda3:/c/Users/Tyler/miniconda3/Library/mingw-w64/bin:/c/Users/Tyler/miniconda3/Library/usr/bin:/c/Users/Tyler/miniconda3/Library/bin:/c/Users/Tyler/miniconda3/Scripts:/c/Users/Tyler/AppData/Local/Microsoft/WindowsApps:/c/Users/Tyler/AppData/Local/Programs/Microsoft VS Code/bin:/usr/bin/vendor_perl:/usr/bin/core_perl

Is this what you are looking for?

Thanks, Tyler.

@tyler477
Copy link

I have just updated Visual Studio to the latest September 2020 version. But I still have received
this same error when trying "bash.exe build_raven", from both CMD and GitBash.

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

The Path is correct (Visual Studio is there). @joshua-cogliati-inl I need your expertise here.

@joshua-cogliati-inl
Copy link
Contributor

joshua-cogliati-inl commented Oct 27, 2020

Hm, that used to mean that VS90COMNTOOLS is not set, but I thought that newer versions of visual studio did not need it set. (As described in https://github.com/idaholab/raven/wiki/installationWindowsOld )

@tyler477
Copy link

hmm... I will keep trying to troubleshoot this. Thanks for your support @alfoa and @joshua-cogliati-inl!

@joshua-cogliati-inl
Copy link
Contributor

Also, usually we run in the git bash environment, instead of just running bash.exe when we need it. That might make a difference.

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

@tyler477 mybe an option can be to follow the instructions at https://github.com/idaholab/raven/wiki/installationWindowsOld#2-let-the-build-system-know-where-to-find-the-compiler

(it should not be required but you can give a shoot and let us know maybe? )
Sorry for this.

@alfoa
Copy link
Collaborator

alfoa commented Oct 27, 2020

@tyler477 I am going to try to re-install the code with the latest versions of visual studio (starting from scratch) to see if I can replicate the problem.

@tyler477
Copy link

tyler477 commented Oct 27, 2020

@alfoa I will try this thank you! So sorry for the trouble.

I am first going to try and reinstall Visual Studio to see this works.

@tyler477
Copy link

@alfoa Thank you so much for your help! I think I've finally got it working... the issue appeared to be that I had the wrong version of Visual Studio installed. Before I had the Visual Studio Code which was updated to 2020 and I deleted it and installed Visual Studio 2019. It no longer gave me the "vcvarsall.bat" error and is currently running tests to ensure proper raven installation.

Thank you again for your time to help me troubleshoot this!

@alfoa
Copy link
Collaborator

alfoa commented Oct 29, 2020

@tyler477 I am really glad you solved the problem.

Closing the issue

@alfoa alfoa closed this as completed Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants