[package] boost/1.70-1.80: Errors with cross-compilation to armv8 following latest recipe update #14767
Comments
evansneath
changed the title
|
You may have to duplicate |
|
@SpaceIm We have a similar problem. Duplicate section did not help. |
|
Can you try again with modifications in #14776 please? (still with a |
|
@SpaceIm, duplication Even though this fixes the issue, I'm not sure this is a suitable long-term fix for this package with conan v1 users since it forces an addition to the optional Thank you for the workaround. |
|
@evansneath I understand, but I think there is nothing conan-center recipes migrated to conan v2 can do to have 100% support of legacy conan v1 profiles, since AFAIK conan client breaks itself this convention in all conan v2 build helpers (like it breaks /cc @memsharded |
|
|
Latest RREV of boost recipe in conan-center doesn't support conan client < 1.53.0, and it should raise an error if you try to run conan command against this RREV: |
|
@SpaceIm, that makes sense. We'll add this section to all of our conan profiles. Looks like the best mitigating factor going forward is to specifically pin our required third-party packages to specific RREVs in order to shelter our build process from the upcoming v2 migration churn. |
|
yes: https://github.com/conan-io/conan-center-index/blob/master/docs/consuming_recipes.md Otherwise, I think conan-center (or conan) doc lacks documentation to explain how a user profile should be written to be conan v1/v2 compatible (due to lack of backward compatibility of legacy env vars, and forward compatibility of new buildenv vars & config), something like this for example: toolchain=aarch64-linux-gnu
[settings]
os=Linux
arch=armv8
compiler=gcc
compiler.version=7
compiler.libcxx=libstdc++11
build_type=Release
[conf]
# for conan v2 recipes
tools.build:compiler_executables.c=$toolchain-gcc
tools.build:compiler_executables.cpp=$toolchain-g++
tools.cmake.cmaketoolchain:generator=Ninja
tools.cmake.cmaketoolchain:user_toolchain=path/to/my_toolchain.cmake
tools.gnu:make_program=make
[buildenv]
# for conan v2 recipes as well
CHOST=$toolchain
CC=$toolchain-gcc
CXX=$toolchain-g++
[env]
# for conan v1 recipes
CHOST=$toolchain
CC=$toolchain-gcc
CXX=$toolchain-g++
CONAN_CMAKE_GENERATOR=Ninja
CONAN_CMAKE_TOOLCHAIN_FILE=path/to/my_toolchain.cmake
CONAN_MAKE_PROGRAM=makeor better with jinja profile: {% set toolchain = "aarch64-linux-gnu" %}
[settings]
os=Linux
arch=armv8
compiler=gcc
compiler.version=7
compiler.libcxx=libstdc++11
build_type=Release
[conf]
{# for conan v2 recipes #}
tools.build:compiler_executables.c={{ toolchain }}-gcc
tools.build:compiler_executables.cpp={{ toolchain }}-g++
tools.cmake.cmaketoolchain:generator=Ninja
tools.cmake.cmaketoolchain:user_toolchain=path/to/my_toolchain.cmake
tools.gnu:make_program=make
[buildenv]
{# for conan v2 recipes as well #}
CHOST={{ toolchain }}
CC={{ toolchain }}-gcc
CXX={{ toolchain }}-g++
[env]
{# for conan v1 recipes #}
CHOST={{ toolchain }}
CC={{ toolchain }}-gcc
CXX={{ toolchain }}-g++
CONAN_CMAKE_GENERATOR=Ninja
CONAN_CMAKE_TOOLCHAIN_FILE=path/to/my_toolchain.cmake
CONAN_MAKE_PROGRAM=makeor a compatiblity matrix between legacy env vars & new config |
|
This is really useful input. We'll be making these changes across all of our profiles. Thanks again for the help. |
Description
Following the latest commit c679b7c6f5642fc49b6a2b1cbb9ecf2f05dbf3c6 with modifications to update the boost recipe to support conan v2, cross-compilation builds of boost from linux x86-64 to linux arm-64 now fail to build.
This is confirmed to be an issue relating only to the latest commit due to cross-compilation working fine until yesterday and with showing successful building using the previous recipe revision (cfb90226b9dfe2f948b861b54ef5dab6).
Package and Environment Details
Conan profile
Contents of
profiles/linux-arm-64Steps to reproduce
Fails (see logs below)
Succeeds (using previous recipe revision):
Logs
Click to expand log
The text was updated successfully, but these errors were encountered: