libmamba/2024.09.30 package update #29763
Conversation
octo-sts
bot
commented
Oct 1, 2024
octo-sts
bot
commented
octo-sts
bot
added
request-version-update
|
Open AI suggestions to solve the build error: |
|
Open AI suggestions to solve the build error: |
|
I think the issue because of we don't have |
|
Based on the error message, the issue is related to yaml-cpp library type mismatch during CMake configuration. The error indicates that the build expects a static library but found a shared library instead. Here are some steps to fix this:
dependencies:
build:
- yaml-cpp-static
environment:
CXXFLAGS: "-DYAML_CPP_STATIC_DEFINE"
pipeline:
- uses: cmake/configure
with:
configure-args: |
-DYAML_BUILD_SHARED_LIBS=OFF
-DBUILD_SHARED_LIBS=OFF
pipeline:
- uses: cmake/configure
with:
configure-args: |
-DMAMBA_FORCE_DYNAMIC_LIBS=ON |
|
Changes summary: Total changes: 15468 Total commits: 330
GitHub compare URL: mamba-org/mamba@25cdc05...9fc7b99 |
|
I have been unable to get this to build for main and all sub packages. The closest is by using build options forcing shared libraries which will successfully build the main package but then subpackage py3-libmambapy and micromamba fail to build. micromamba assumes static libraries as noted @ https://github.com/mamba-org/mamba/blob/c511d5c9f71165c0af75d916b46355a980e292f8/CMakeLists.txt#L70 but wolfi does not have static libs for yaml-cpp or reproc as it expects. py3-libmambapy fails as it can't find libmamba dependencies. Build of previous version before this version bump is successful. |
|
Gen AI suggestions to solve the build error: Based on the error message shown, it appears the main issue is with authentication: Here are a few suggestions to resolve this:
The core package definition looks correct - the error is related to the build environment authentication rather than the package configuration itself. Would you like me to elaborate on any of these suggestions? |
|
I've spent some time on this and explored two paths...
I've pretty much got the first one working so may push a PR up for that in a bit, still not sure that's the best out of the two options mind. |
Signed-off-by: wolfi-bot <[email protected]>
…now expecting static Also had to add `CXXFLAGS: "-fPIC"` as the build failed without it, other packages seem to do the same. The subpackage changes were needed as the binding files are in the right location with the default build now. Added new required python dependencies. Signed-off-by: James Rawlings <[email protected]>
rawlingsj
force-pushed
the
wolfictl-a804a634-a79e-41f4-99f6-df5e31aa4245
branch
from
62b589e to
8a308df
Compare
|
ok, the shared library approach (option 1 from above) was becoming toilsome so I went with option 2, patched the project to use shared libs. Also needed a few extra deps and changes to get a successful build. Package tests are passing too. |
Package libmamba: Click to expand/collapsePackage libmamba: Package py3-libmambapy: Click to expand/collapsePackage py3-libmambapy: Package libmamba-dev: Click to expand/collapsePackage libmamba-dev: Package micromamba: Click to expand/collapsePackage micromamba: Package mamba-package: Click to expand/collapsePackage mamba-package: |
octo-sts
bot
added
the
bincapz/pass
