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

GitHub CI issues for Base64::Native on Windows #2

Open
japhb opened this issue Jul 22, 2021 · 10 comments
Open

GitHub CI issues for Base64::Native on Windows #2

japhb opened this issue Jul 22, 2021 · 10 comments

Comments

@japhb
Copy link

japhb commented Jul 22, 2021

I am building another module on top of Base64::Native, and can't get the GitHub Workflow CI to work on Windows because of this error from the zef build phase during dependency installation:

===> Building: Base64::Native:ver<0.0.4>:auth<cpan:WARRINGD>
[Base64::Native] process_begin: CreateProcess(NULL, cl -I src -c /nologo /MT /std:c++latest /Ox /GL /DNDEBUG /DWIN32 /DAO_ASSUME_WINDOWS98 -DMVM_HEAPSNAPSHOT_FORMAT=2 -D_GNU_SOURCE /Fosrc/base64.obj src/base64.c, ...) failed.
[Base64::Native] make (e=2): The system cannot find the file specified.
[Base64::Native] mingw32-make: *** [Makefile:15: src/base64.obj] Error 2
[Base64::Native] The spawned command 'make' exited unsuccessfully (exit code: 2, signal: 0)
[Base64::Native]   in method build at C:\Users\runneradmin\.zef\store\Base64-Native-0.0.4.tar.gz\Base64-Native-0.0.4\Build.pm6 line 25
[Base64::Native]   in sub MAIN at C:\Users\runneradmin\.zef\store\Base64-Native-0.0.4.tar.gz\Base64-Native-0.0.4\Build.pm6 line 32
[Base64::Native]   in block <unit> at C:\Users\runneradmin\.zef\store\Base64-Native-0.0.4.tar.gz\Base64-Native-0.0.4\Build.pm6 line 5
[Base64::Native]   in block <unit> at -e line 1
===> Building [FAIL]: Base64::Native:ver<0.0.4>:auth<cpan:WARRINGD>

Your badges indicate that it's passing on AppVeyor, but when I click on the Windows badge, AppVeyor tells me Project not found or access denied. so I can't see when it passed or with which version of Rakudo, to compare against what GitHub Workflows is using.

Would you mind taking a look and checking whether it still passes for you?

For what it's worth, this is the Rakudo version that GHWF is apparently using:

Downloading rakudo 2021.06 from https://rakudo.org/dl/rakudo/rakudo-moar-2021.06-01-win-x86_64-msvc.zip
Extracting archive
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$ErrorActionPreference = 'Stop' ; try { Add-Type -AssemblyName System.IO.Compression.FileSystem } catch { } ; [System.IO.Compression.ZipFile]::ExtractToDirectory('D:\a\_temp\b905bf32-7353-4c2c-8fa5-0b393b090faf', 'D:\a\_temp\ff130b0d-9b66-4b96-8b5c-53c321b39616')"
Successfully installed rakudo into C:\hostedtoolcache\windows\rakudo\2021.06-01\x86_64
dwarring added a commit that referenced this issue Jul 22, 2021
- replace Travis with github workflow, including Windows.
- not sure what's with appveyor. try to fix proejct link, as least
@dwarring
Copy link
Contributor

I just kicked off a build. Appveyor project now seems to be here

Also made first attempt at a github testing build failing with missing nmake in LibraryMake dependency

@japhb
Copy link
Author

japhb commented Jul 22, 2021

Hmmm, so passed in AppVeyor for you at least, that's good. Perhaps something that Chocolatey provides that needs to be manually installed in a GitHub workflow? Ah yes, I can see choco install make followed by choco install mingw, that looks promising at least.

dwarring added a commit that referenced this issue Jul 22, 2021
@dwarring
Copy link
Contributor

Appveyor working at least, but still trying to figure out github windows testing. choco installs work on latest attempt , but still not picking up nmake.

@japhb
Copy link
Author

japhb commented Jul 26, 2021

(For reference, 8a0e5ef is because of this issue.)

@dwarring
Copy link
Contributor

hopefully fixed in db39b0d. I changed the Build.pm6 to rety using gcc and make, if the initial Visual Tools flavored build fails on Windows.

@dwarring
Copy link
Contributor

further refined after reading croservices/cro#105. Looks for make or gmake so hopefully also works with Strawberry Perl

@dwarring
Copy link
Contributor

dwarring commented Jan 12, 2022

Hmm, LibraryMake dependency is still failing its tests and currently needs a forced install.

@dwarring
Copy link
Contributor

I'm thinking of trying another approach.. Maybe the win dll could be built as a github build action and distributed rather than being built at installation.

dwarring added a commit that referenced this issue Jan 14, 2022
@dwarring
Copy link
Contributor

Have set-up a github workflow to build the DLL. Getting a github test failure on HTTP::Status, as aby-product of switching to Native::Compile which has this as a depdendency.

@dwarring
Copy link
Contributor

Now working reasonably well on master, except for need to force install LibraryMake. I've raised a PR for this.

Runs a build workflow to update DLL (if needed), before running tests. DLL is distributed on Windows systems, so there's no need to build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants