-
Notifications
You must be signed in to change notification settings - Fork 585
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
Apple Silicon Error FS0193: The specified file name or path is too long #2626
Comments
Welcome to the FAKE community! Thank you so much for creating your first issue and therefore improving the project! |
Can you try setting that environment variable and running in verbose mode and pasting the output? Maybe that can give a hint to a potential workaround. |
Hey, sadly that doesn't yield any additional information. I See the fsc-args and directly after that I get:
|
I'd try the following:
|
Hey, I managed to build it using When using the "original" output-path I don't get any error, nonetheless no output-file is created. after running the directory |
Can you check that no anti-virus program is just deleting the file? Technically, we add the hash to ensure to recompile when something changes, we could do that differently but there is really no reason why that wouldn't work on MACs |
Hey, I can manually create the file without any problem (the alternative would have been very weird) Maybe someone else with a M1-Mac could confirm that this doesn't work? |
Then you might have a workaround: Build manually and rename the file :) |
hey, I was trying to find the problem in fake-cli and it actually happens somewhere in FSharp.Compiler.Service. I tried updating FSCS to the latest (41.0.1) version and fixed all the tiny problems locally, however I run into MissingMethodExceptions related to PrintFormat in FSharp.Core (maybe some dependency built with a very old FSharp.Core?) Any hints how to properly upgrade dependencies without destroying something on some other end? However the new FSCS version made the original problem go away. P.S.: the exception I get is The forked repo is here |
I can confirm this does not work at the moment. Unfortunately I cannot add anything to help with debugging. My setup:
And FAKE:
|
I had this exact problem, but I think I found a workaround. So the problem is with .NET Arm64 version, when I switched to .NET x64 version it started to working. |
Could this be the same as dotnet/runtime#63240 ? |
I'm having the same issue. My configuration is almost exactly as is @TomiLahtinen 's. |
@michaljosek, Can you give more details on your switch to .NET x64? |
@malclear I uninstalled ARM64 version. You can navigate to Microsoft page and download x64 version. Here you can read about Breaking changes - installation location for ARM64/x64. |
(If my diagnosis above is correct, this should be fixed in .NET 6.0.3, by dotnet/runtime#64266 .) |
problem seems to still exist on my system at least, with an empty build file
edit: realized I could just run
|
Is there a way to force FAKE to run with a particular SDK version? My issue is that I need a net6 SDK to build my project, but I cannot run FAKE itself with net6 because of this bug. The only workaround I've found so far is to uninstall the net6 SDK, run FAKE far enough through the build that something seems to get cached on disk that prevents recurrence of this bug when running again, then re-installing the net6 SDK. Needless to say this isn't exactly ergonomic and has turned out to be error-prone for other reasons. |
@macklindemetrix You can choose to use a specific version of dotnet SDK, by specifying it in a global.json file, see https://learn.microsoft.com/en-gb/dotnet/core/tools/global-json. If you want to run FAKE using one Sdk, and want to run the app using another, I believe this can be accomplished using multiple global.json files. |
Does it still fail? Is only .NET 7 supported on Mac ARM? |
Description
When running
dotnet fake run build.fsx
(with a super-minimalistic build.fsx) on my MacBook Air (M1) I keep getting the error:I tried several versions of
fake-cli
(including the latest prereleases) and all of them give the same result.Verbose output shows me the
fsc
arguments and fails with said error.Any help would be greatly appreciated.
Repro steps
A small repro can be found at krauthaufen/FakeAppleProblem
Known workarounds
none, sadly
Related information
MacOS X 12.0.1
dotnet --info
The text was updated successfully, but these errors were encountered: