-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[bug] abseil/20230802.1: link failure #25071
Comments
The same story is with protobuf. |
https://github.com/conan-io/conan/issues would be a better place for this question, conan-center is not responsible of the design of files generated by Your issue might be related to conan-io/conan#13560, but I can't say for sure since you didn't share full log. |
Can you move it into conan/issues, or should I resubmit? |
I'm not part of conan team, I can't move issues. |
resubmitted |
Closing as duplicated, lets follow up better in the Conan repo ticket |
Description
I have a problem linking against gRPC, but the real problem seems to be abseil package
Package and Environment Details
Linux
cmake 3.21.2
conan 2.6.0
Conan profile
Host profile:
[settings]
arch=x86_64
build_type=Release
compiler=gcc
compiler.cppstd=gnu17
compiler.libcxx=libstdc++11
compiler.version=13
os=Linux
[conf]
Build profile:
[settings]
arch=x86_64
build_type=Release
compiler=gcc
compiler.cppstd=gnu17
compiler.libcxx=libstdc++11
compiler.version=13
os=Linux
[conf]
Steps to reproduce
Take test_package.cpp source file from abseil recipe
https://github.com/conan-io/conan-center-index/blob/master/recipes/abseil/all/test_package/test_package.cpp
Create CMakeLists.txt
and create the following conanfile.txt:
Yes, require grpc (which requires abseil, as we know)
Now run
and look at build/Release/generators/absl-release-x86_64-data.cmake
we see:
set(abseil_LIBS_RELEASE )
The list is empty.
Now delete build directory, add abseil into conanfile.txt, and do "conan install" again
Now in absl-release-x86_64-data.cmake we see
set(abseil_LIBS_RELEASE absl_flags_parse absl_log_flags .. and the long list of libraries)
Is this behavior by design, or is it a bug?
My point here is that I do not know what is abseil and I do not care.
What I need is grpc. I request grpc, I "find_package(gRPC)", and then linking fails because abseil libraries are missing
So, let me repeat my question.
Is this behavior by design, or is it a bug?
Logs
without requires/abseil/20230802.1:
lots of
test_package.cpp:(.text.startup+0x365): undefined reference to ...
with requires/abseil/20230802.1:
build is ok
The text was updated successfully, but these errors were encountered: