Link checker cannot find dependencies for multi-output recipe in 3.28.3 #5136
Assignees
Labels
in-progress
issue is actively being worked on
severity::3
major; broken functionality with a workaround
source::community
catch-all for issues filed by community members
type::bug
describes erroneous operation, use severity::* to classify the type
Comments
carterbox
added
the
type::bug
carterbox
added a commit
to MementoRC/staged-recipes
that referenced
this issue
Jan 12, 2024
This version of conda-build was not able to correctly locate libc for satisfying links in as multioutput recipe. conda/conda-build#5136
10 tasks
5 tasks
|
@conda-forge/help-c-cpp, I discovered this bug while reviewing on staged-recipes. Pinging y'all for awareness. |
1 task
11 tasks
kenodegard
added
severity::1
3 tasks
|
This is fixed by #5138 |
3 tasks
kenodegard
added
in-progress
|
lowered severity since there are workarounds like adding there are currently two candidate fixes, so for those interested please take a look and leave feedback:
|
|
Thanks, @kenodegard @minrk ! I appreciate your quick attention. |
3 tasks
3 tasks
kenodegard
added a commit
that referenced
this issue
Jan 17, 2024
* Add test for deleted files in which_package * Add which_package case-insensitivity test on Win * Restore pre-3.28 behavior for which_package * Add regression test for #5136 --------- Signed-off-by: Marcel Bargull <marcel.bargull@udo.edu> Co-authored-by: Ken Odegard <kodegard@anaconda.com>
|
thanks to @minrk and @mbargull for helping to debug and proposing fixes #5141 has been merged and we're now working on a patch release ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I believe there is an error with the link checker in conda-build version 3.28.3.
When building the libsecp256k1 recipe from this pull request, we get a missing dependency error as follows:
It seems that the link checker cannot find libc.so.6 for the libsecp256k1 output even though the compiler jinja template is included in the build requirements section for that output.
The same requirements are used for the libsecp256k1-2 output, but the link checker can find libc there.
I was able to recproduce the issue locally, but only with conda-build 3.28.3.
Earlier versions of conda-build including 3.26, 3.27 did not check the links of libsecp256k1.so (because it is a symlink?), and so do not raise the error. 3.28.2 checks the links but is able to find libc.
Conda Details
conda infoconda configconda listThe text was updated successfully, but these errors were encountered: