Windows GCC Executable Fails From WSL

[mateusz-]

Windows Version

Microsoft Windows [Version 10.0.19045.4291]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.10.16

Distro Version

20.04

Other Software

arm-none-eabi-gcc.exe (Arm GNU Toolchain 12.2.Rel1 (Build arm-12.24)) 12.2.1 20221205

Repro Steps

1. Download GCC toolchain from arm (see version noted in "Other Software").
2. Create a main.c with the following contents:

   int main(void) {
           return 0;
   }
   
   void _close(void) {}
   void _getpid(void) {}
   void _kill(void) {}
   void _lseek(void) {}
   void _read(void) {}
   void _write(void) {}
   void _sbrk(void) {}
   void _exit(int val) { while(1) {} }```
   

3. Build
   ./arm-none-eabi-gcc.exe main.c -v

Expected Behavior

No compilation error.

Performing the same steps from Windows PowerShell - everything succeeds.

Actual Behavior

Compilation errors with:
arm-none-eabi-gcc.exe: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Issue running ARM cross compiler on WSL (#1048), similarity score: 0.73
• support legacy vsyscall - Segmentation Fault using a gcc cross compiler (#1462), similarity score: 0.71
• Compiling arm gcc crashes on wsl 2 because virtual memory exhausted (#5295), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[mateusz-]

WslLogs-2024-05-16_07-43-12.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel found: 'c:\Users\e373016\WSL2\usbip-bzImage'
Appx package is not installed

[OneBlue]

Thank you for reporting this @mateusz-. I'm not seeing anything failing in the WSL logs, and based on the error message, it looks like a configuration / path issue on the gcc side so this unfortunately not something that WSL can fix.

Closing since the issue is coming from a third party executable.