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.

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

ci: fix build error on windows #179

Merged
merged 1 commit into from
Nov 26, 2024
Merged

ci: fix build error on windows #179

merged 1 commit into from
Nov 26, 2024

Conversation

malor
Copy link
Member

@malor malor commented Nov 26, 2024

See sfackler/rust-openssl#2149.

Apparently, in the Windows runner, commands executed in a run block will use the version of Perl built into MinGW instead of the one installed in the system, which breaks the openssl build because one of the expected Perl modules can't be found.

There are different ways to fix this. The one suggested in this PR is returning back to using the cargo action for "normal" (not cross compilation) builds like it used to work before. My understanding is that it helps by running cargo directly as opposed to running it from Bash.

Alternatively, we could bypass the corresponding build steps in openssl by providing locations of openssl source code via environment variables like it is suggested in the rust-openssl issue linked above.

.github/workflows/release.yml Outdated Show resolved Hide resolved
.github/workflows/release.yml Outdated Show resolved Hide resolved
@malor malor force-pushed the release branch 3 times, most recently from 8cf1228 to 526a589 Compare November 26, 2024 21:22
See sfackler/rust-openssl#2149.

Apparently, in the Windows runner, commands executed in a `run` block
will use the version of Perl built into MinGW instead of the one
installed in the system, which breaks the openssl build because one of
the expected Perl modules can't be found.

There are different ways to fix this. The one suggested in this PR is
returning back to using the cargo action for "normal" (not cross
compilation) builds like it used to work before. My understanding is
that it helps by running cargo directly as opposed to running it from
Bash.

Alternatively, we could bypass the corresponding build steps in openssl
by providing locations of openssl source code via environment variables
like it is suggested in the rust-openssl issue linked above.
@malor malor merged commit a93b364 into master Nov 26, 2024
8 checks passed
@malor malor deleted the release branch November 26, 2024 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants