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

Cannot run Intel Compiler ICC or ICPC command in WSL #2608

Closed
macxfadz opened this Issue Oct 26, 2017 · 22 comments

Comments

Projects
None yet
10 participants
@macxfadz

macxfadz commented Oct 26, 2017

I recently installed Fresh Windows 10 (Pro) Fall creators update (General Release ,not an Insider Build).

Enable Linux Subsystem and installed Ubuntu App through Windows 10 App store.
Install relevant updates in Windows and WSL
Install Intel Parallel Studio 2018 - Here Parallel studio 2018 comes with .tgz distribution I extract all the content in to a folder in windows side and mount it from WSL bash and install it from there.Further guide lines obtain from here - Intel Guide & Compile guide & Intel setup guide

  • After successful installation I set environment variables as they mentioned.set Atchitecture to intel64 and Platform to Linux

  • Create simple C++ source file tried to compile it using icpc intel compiler command but WSL cannot fork the process and identify the command

Please help on this matter. How to configure intel C./C++ compiler in WSL correctly?

icpc_error
icp2
icpc3
icpc4

@therealkenc

This comment has been minimized.

Show comment
Hide comment
@therealkenc

therealkenc Oct 27, 2017

Collaborator

Need a gist of the strace so we can check out the EINVAL.

strace -ff icpc a.cpp 2> icpc.strace

Also the output of ver from the windows command line. Gonna say #1005, but that's just a guess absent the trace.

Collaborator

therealkenc commented Oct 27, 2017

Need a gist of the strace so we can check out the EINVAL.

strace -ff icpc a.cpp 2> icpc.strace

Also the output of ver from the windows command line. Gonna say #1005, but that's just a guess absent the trace.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Oct 27, 2017

@therealkenc cannot trace it..
Output -
icpc5

macxfadz commented Oct 27, 2017

@therealkenc cannot trace it..
Output -
icpc5

@therealkenc

This comment has been minimized.

Show comment
Hide comment
@therealkenc

therealkenc Oct 27, 2017

Collaborator

icpc is not in your path, which is not a WSL thing.

I was referring to the following from you screencap in the OP:

icpc: error #10103: can't fork process: Invalid argument
Collaborator

therealkenc commented Oct 27, 2017

icpc is not in your path, which is not a WSL thing.

I was referring to the following from you screencap in the OP:

icpc: error #10103: can't fork process: Invalid argument
@onomatopellan

This comment has been minimized.

Show comment
Hide comment
@onomatopellan

onomatopellan Oct 27, 2017

@macxfadz You need to call source psxevars.sh every time you open bash.exe in order to use icpc or get the strace.

onomatopellan commented Oct 27, 2017

@macxfadz You need to call source psxevars.sh every time you open bash.exe in order to use icpc or get the strace.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Oct 28, 2017

@onomatopellan strace was generated but, .out or compiled binary output couldn't generated,please need your help on invoking intel compiler.
icpc6

macxfadz commented Oct 28, 2017

@onomatopellan strace was generated but, .out or compiled binary output couldn't generated,please need your help on invoking intel compiler.
icpc6

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Oct 28, 2017

@therealkenc here is the strace file ,that was generated

icpc.strace.txt

macxfadz commented Oct 28, 2017

@therealkenc here is the strace file ,that was generated

icpc.strace.txt

@therealkenc

This comment has been minimized.

Show comment
Hide comment
@therealkenc

therealkenc Oct 28, 2017

Collaborator
open("/tmp/icpcdashvzbvylx", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
close(3)                                = 0
unlink("/tmp/icpcdashvzbvylx")          = 0
rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 0x7f9ed0b954b0}, {0x52a230, [INT], SA_RESTORER|SA_RESTART, 0x7f9ed0b954b0}, 8) = 0
{SIG_DFL, [], SA_RESTORER, 0x7faca86654b0}, 8) = 0
[... more unnotable rt_sigactions]
mmap(NULL, 10489856, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9ed00d0000
clone(child_stack=0x7f9ed0acffff, flags=CLONE_VFORK|SIGCHLD) = -1 EINVAL (Invalid argument)

Which sure looks like #1005; but you say you are on 16299 FCU -- still no ver output from windows command prompt. CLONE_VFORK|SIGCHLD was addressed back in Feburary (message) circa 15046. Anyway, "there's your problem".

Collaborator

therealkenc commented Oct 28, 2017

open("/tmp/icpcdashvzbvylx", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
close(3)                                = 0
unlink("/tmp/icpcdashvzbvylx")          = 0
rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 0x7f9ed0b954b0}, {0x52a230, [INT], SA_RESTORER|SA_RESTART, 0x7f9ed0b954b0}, 8) = 0
{SIG_DFL, [], SA_RESTORER, 0x7faca86654b0}, 8) = 0
[... more unnotable rt_sigactions]
mmap(NULL, 10489856, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9ed00d0000
clone(child_stack=0x7f9ed0acffff, flags=CLONE_VFORK|SIGCHLD) = -1 EINVAL (Invalid argument)

Which sure looks like #1005; but you say you are on 16299 FCU -- still no ver output from windows command prompt. CLONE_VFORK|SIGCHLD was addressed back in Feburary (message) circa 15046. Anyway, "there's your problem".

@dmey

This comment has been minimized.

Show comment
Hide comment
@dmey

dmey Nov 2, 2017

@therealkenc, I am having the same issue: Microsoft Windows [Version 10.0.16299.19].
Let me know if you need more logs.
Thanks for looking into this.

dmey commented Nov 2, 2017

@therealkenc, I am having the same issue: Microsoft Windows [Version 10.0.16299.19].
Let me know if you need more logs.
Thanks for looking into this.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Dec 4, 2017

@therealkenc any luck ? anyone ran Intel C/C++ compiler successfully in WSL?

macxfadz commented Dec 4, 2017

@therealkenc any luck ? anyone ran Intel C/C++ compiler successfully in WSL?

@therealkenc

This comment has been minimized.

Show comment
Hide comment
@therealkenc

therealkenc Dec 4, 2017

Collaborator

I can't tell from the strace alone what is causing the EINVAL. The lead up looks alright, assuming I am not staring something in the face (I might). The license terms for Intel Parallel Studio do cause somewhat of an unfortunate drag on investigation. It would be worth contacting your Intel sales rep. It would also be worth trying Insiders, because CLONE_VFORK had major surgery as of 17046, and there is a better than zero chance this sorted itself.

Collaborator

therealkenc commented Dec 4, 2017

I can't tell from the strace alone what is causing the EINVAL. The lead up looks alright, assuming I am not staring something in the face (I might). The license terms for Intel Parallel Studio do cause somewhat of an unfortunate drag on investigation. It would be worth contacting your Intel sales rep. It would also be worth trying Insiders, because CLONE_VFORK had major surgery as of 17046, and there is a better than zero chance this sorted itself.

@jstarks

This comment has been minimized.

Show comment
Hide comment
@jstarks

jstarks Dec 4, 2017

Member

CLONE_VFORK without CLONE_VM would fail before 17046 but should work fine now. So this may be fixed in recent insider builds.

Member

jstarks commented Dec 4, 2017

CLONE_VFORK without CLONE_VM would fail before 17046 but should work fine now. So this may be fixed in recent insider builds.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Dec 4, 2017

@therealkenc @jstarks , as you guys mentioned , with next Windows 10 this issue will be resolved right?
flags=CLONE_VFORK|SIGCHLD) = -1 EINVAL (Invalid argument)

macxfadz commented Dec 4, 2017

@therealkenc @jstarks , as you guys mentioned , with next Windows 10 this issue will be resolved right?
flags=CLONE_VFORK|SIGCHLD) = -1 EINVAL (Invalid argument)

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 4, 2017

Member

@macxfadz - Yes, where next means the release after Fall Creators Update.

Member

sunilmut commented Dec 4, 2017

@macxfadz - Yes, where next means the release after Fall Creators Update.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Dec 5, 2017

@sunilmut , next implies next Windows 10 major update release on April or May :) ,Thank you for the confirmation.

macxfadz commented Dec 5, 2017

@sunilmut , next implies next Windows 10 major update release on April or May :) ,Thank you for the confirmation.

@BopngMa

This comment has been minimized.

Show comment
Hide comment
@BopngMa

BopngMa Jan 4, 2018

It also occurs to me!!!

Has this problem solved in the insider version? Anyone tested ?

How to install the insider version?

Thanks

BopngMa commented Jan 4, 2018

It also occurs to me!!!

Has this problem solved in the insider version? Anyone tested ?

How to install the insider version?

Thanks

@kei2e

This comment has been minimized.

Show comment
Hide comment
@kei2e

kei2e Mar 15, 2018

It seems to have been resolved in insider build: Had the same problem, but now works fine after updating to 17115.

kei2e commented Mar 15, 2018

It seems to have been resolved in insider build: Had the same problem, but now works fine after updating to 17115.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Mar 15, 2018

When we are going to have next major update of Windows 10 1803? this coming April?

macxfadz commented Mar 15, 2018

When we are going to have next major update of Windows 10 1803? this coming April?

@DarthSpock

This comment has been minimized.

Show comment
Hide comment
@DarthSpock

DarthSpock Mar 15, 2018

It will be in available in early April. They released a KB a couple days ago that was forcefully installed upon internet connectivity being established to assist upgrading to 1803. I doubt the forced KB would rear it's head in a corporate network but your personal computer will be affected. Of course you can uninstall it (but considering the advantages to WSL and Windows that will be gained I wouldn't).

DarthSpock commented Mar 15, 2018

It will be in available in early April. They released a KB a couple days ago that was forcefully installed upon internet connectivity being established to assist upgrading to 1803. I doubt the forced KB would rear it's head in a corporate network but your personal computer will be affected. Of course you can uninstall it (but considering the advantages to WSL and Windows that will be gained I wouldn't).

@tianyikillua

This comment has been minimized.

Show comment
Hide comment
@tianyikillua

tianyikillua Apr 30, 2018

I confirm that the problem is now solved within 1803.

tianyikillua commented Apr 30, 2018

I confirm that the problem is now solved within 1803.

@jstarks jstarks added the fixedin1803 label Apr 30, 2018

@jstarks

This comment has been minimized.

Show comment
Hide comment
@jstarks

jstarks Apr 30, 2018

Member

Great, thanks for confirming.

Member

jstarks commented Apr 30, 2018

Great, thanks for confirming.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz May 1, 2018

@tianyikillua thank you for the confirmation.

macxfadz commented May 1, 2018

@tianyikillua thank you for the confirmation.

@macxfadz

This comment has been minimized.

Show comment
Hide comment
@macxfadz

macxfadz Jun 2, 2018

actually, I installed WSL 18.04 with Windows 10 1803 same thing happened again... but I found a fix for this issue , hope this might help you.
bashrc
select
setpathandargs
checking

macxfadz commented Jun 2, 2018

actually, I installed WSL 18.04 with Windows 10 1803 same thing happened again... but I found a fix for this issue , hope this might help you.
bashrc
select
setpathandargs
checking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment