Closed uilianries closed 4 years ago
this is the continuation of https://github.com/conan-io/conan-center-index/issues/213
I guess the core question is: How can we identify installer packages automatically?
IIRC Conan center hook is able to do it, it checks if os_arch and build_arch are declared only
Another take on this problem could that this line is the cause of the bug, but it would only solve stdlib abi issue, not glibc abi issues.
That's it: https://github.com/conan-io/hooks/blob/master/hooks/conan-center.py#L131
The problem is that sometimes we do have more settings for the build process, which are only getting deleted in package()
. So we can't know before a build for sure that it is an installer
That's it: https://github.com/conan-io/hooks/blob/master/hooks/conan-center.py#L131
The problem is that sometimes we do have more settings for the build process, which are only getting deleted in
package()
. So we can't know before a build for sure that it is an installer
That's true, it's fragile, maybe we can check it based on package_id
fixed by #2062
When building installer packages (cmake, bison, ninja, meson ...) sometimes we have a problem related to the C library version which is incompatible to the present in the current Docker image. In the past, Bincrafters opted to use CentOS6 which solved 99% of cases, but now we using Ubuntu 16.04 (GCC5) which is failing when we need to build a package with GCC 4.9 because conanio/gcc49 is Ubuntu 14.04.
Suggestion, identify installer packages and use a old Linux distro when building, CentOS6 for instance
/cc @ericLemanissier
Package and Environment Details (include every applicable attribute)
Conan profile (output of
conan profile show default
orconan profile show <profile>
if custom profile is in use)Steps to reproduce (Include if Applicable)
Logs (Include/Attach if Applicable)
https://github.com/bincrafters/conan-libdrm/runs/379290528