-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Building PowerShell Core on WSL generates error #5194
Copy link
Copy link
Closed
Labels
HacktoberfestPotential candidate to participate in HacktoberfestPotential candidate to participate in HacktoberfestIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
Metadata
Metadata
Assignees
Labels
HacktoberfestPotential candidate to participate in HacktoberfestPotential candidate to participate in HacktoberfestIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
FWIW I do seem to get a valid pwsh built and I can run it. So that is good.
Steps to reproduce
cd /mnt/c/GitHub/PowerShellBTW this is a darn convenient way to build/test for both Windows and Linux. No need to push your changes to origin so you can pull them to Linux to test.
Expected behavior
pwsh builds - no errors.
Actual behavior
Get an error:
Sure enough, the powershell.inc file includes a whole bunch of paths that start with
C:\.Environment data
BTW the root of the problem is that TypeGen dir -
$PSScriptRoot/src/TypeCatalogGen- is not platform specific. It probably should be$PSScriptRoot/src/TypeCatalogGen/$Runtime. Easiest work-around for now isStart-PSBuild -Clean.