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.

Sign up for GitHub

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

Jump to bottom

build on windows, error: plugin process ended by an uncaught signal: 1033 #422

Closed
marco20240618 opened this issue Oct 12, 2022 · 4 comments
Closed

build on windows, error: plugin process ended by an uncaught signal: 1033 #422

marco20240618 opened this issue Oct 12, 2022 · 4 comments

Comments

@marco20240618
Copy link

swift.exe build -c release

error: plugin process ended by an uncaught signal: 1033 <command: d:\tmp\swift-format\.build\plugins\cache\generate_pipeline_plugin.exe>, <output:
>

image
@compnerd
Copy link
Member

As a quick sanity check/workaround, could you please try the following:

path C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\lib\swift\pm\PluginAPI;%Path%
swift build -c release

I suspect that the error 1033 is "dll not found" as we do not inject the path to the plugin API runtime support into Path (there is no rpath equivalent on Windows, Path is the approach) when the plugin is executed, and you happened to actually properly receive an error message for that.

allevato added a commit to allevato/swift-format that referenced this issue Oct 12, 2022
@allevato
Revert the use of generate-pipeline-plugin on Windows platforms.
a4e0c00 
This temporarily removes the use of the plugin only on Windows, where it
is not working properly due to a likely bug in SPM. We can keep the
files checked in for now and updated using the
`Scripts/generate-all-pipelines.sh` script, and those files will be
ignored on other platforms (the plugin will still be used there).

Fixes swiftlang#422.
This was referenced Oct 12, 2022
Closed
Merged
@allevato
Copy link
Member

We had to revert the plugin for other reasons, so can you please pull down the latest changes and try the build again?

@marco20240618
Copy link
Author

As a quick sanity check/workaround, could you please try the following:

path C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\lib\swift\pm\PluginAPI;%Path%
swift build -c release

I suspect that the error 1033 is "dll not found" as we do not inject the path to the plugin API runtime support into Path (there is no rpath equivalent on Windows, Path is the approach) when the plugin is executed, and you happened to actually properly receive an error message for that.

We had to revert the plugin for other reasons, so can you please pull down the latest changes and try the build again?

I pull down the latest code, not working

[5/10] Compiling SystemPackage Errno.swifterror: command Archiving d:\tmp\swift-format\.build\x86_64-unknown-windows-msvc\release\libSwiftSyntax.a failed: unable to spawn process 'ar' (The system cannot find the file specified.
)

image

@compnerd
Copy link
Member

Please use a more recent Swift toolchain. Something like the 2022-10-08-a snapshot should do. Alternatively, workaround this by using set AR=llvm-ar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Revert the use of generate-pipeline-plugin on Windows platforms. allevato/swift-format
3 participants
@compnerd @allevato @marco20240618