You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running conan install ... for the dav1d package, the Installing package dav1d... step makes ninja look for the "nasm" executable without any extension, but the one generated in the build has the extension ".exe". Renaming "nasm.exe" to "nasm" fixes it, but still it remains how to make ninja look for the generated executable with the ".exe" by default.
Complete logs in "How to reproduce it"
-------- Installing package dav1d/1.4.3 (4 of 4) --------
.
.
.
Found ninja-1.12.1 at C:\Users\25\.conan2\p\ninjad9a44352249a5\p\bin\ninja.EXE
dav1d/1.4.3: Meson build cmd: meson compile -C "C:\Users\25\.conan2\p\b\dav1d8a7fc96ebbeaa\b\build-release" -j8
dav1d/1.4.3: RUN: meson compile -C "C:\Users\25\.conan2\p\b\dav1d8a7fc96ebbeaa\b\build-release" -j8
INFO: autodetecting backend as ninja
INFO: calculating backend command to run: C:\Users\25\.conan2\p\ninjad9a44352249a5\p\bin\ninja.EXE -j 8
ninja: error: 'C:/Users/25/.conan2/p/nasm82fc2c9a305c1/p/bin/nasm', needed by 'src/libdav1d.a.p/cpuid.obj', missing and no known rule to make it
dav1d/1.4.3: ERROR:
Package 'e90737b04880f51a4e48d7225fcbe6aa538dc7bd' build failed
dav1d/1.4.3: WARN: Build folder C:\Users\25\.conan2\p\b\dav1d8a7fc96ebbeaa\b\build-release
ERROR: dav1d/1.4.3: Error in build() method, line 92
meson.build()
ConanException: Error 1 while executing
Navigating to C:/Users/25/.conan2/p/nasm82fc2c9a305c1/p/bin/ shows the "nasm.exe" file and renaming it to "nasm", and rerunning conan install ... fixes it.
How to reproduce it
A small repo that has a workflow showing only how it fails when using the 1-failure-nasm profile. repo | workflow.
Locally I used Powershell and on Github Actions it uses MSYS2.
As a quick note, I'd like to highlight that packages in ConanCenter are only built and tested with msvc compiler. That means that support for other compilers might vary, so this might not be a Conan issue, but a recipe issue (in that case it would be needed to be moved to ConanCenter repo).
For reporting against Conan client, in general it is much better to report with a simpler project, something like using a conan new cmake_lib template, that helps a lot to reproduce and fix Conan client issues.
Describe the bug
Environment Details
Conan Profile
Description
When running
conan install ...
for the dav1d package, theInstalling package dav1d...
step makes ninja look for the "nasm" executable without any extension, but the one generated in the build has the extension ".exe". Renaming "nasm.exe" to "nasm" fixes it, but still it remains how to make ninja look for the generated executable with the ".exe" by default.Complete logs in "How to reproduce it"
Navigating to
C:/Users/25/.conan2/p/nasm82fc2c9a305c1/p/bin/
shows the "nasm.exe" file and renaming it to "nasm", and rerunningconan install ...
fixes it.How to reproduce it
A small repo that has a workflow showing only how it fails when using the 1-failure-nasm profile. repo | workflow.
Locally I used Powershell and on Github Actions it uses MSYS2.
Logs
Logs
The text was updated successfully, but these errors were encountered: