I moved on passed this problem by building bootstrap without a toolset and it
uses g++ by default. Then built b2 with a custom "
--user-config=user-config.jam toolset=intel-1913" below.
File user-config.jam:
using intel : 1913 : icpc :
<cflags>"-O2 -fPIC -gcc-name=/opt/gcc/10.2.0/bin/gcc"
<cxxflags>"-O2 -fPIC -gxx-name=/opt/gcc/10.2.0/bin/g++ -std=c++11"
<linkflags>"-O2 -gcc-name=/opt/gcc/10.2.0/bin/gcc
-gxx-name=/opt/gcc/10.2.0/bin/g++"
;
Chris
-----Original Message-----
From: Alain O' Miniussi <alain.miniu...@oca.eu>
Sent: Monday, August 9, 2021 11:09 AM
To: boost-users@lists.boost.org
Cc: Borchert, Christopher B ERDC-RDE-ITL-MS CIV
<christopher.b.borch...@erdc.dren.mil>
Subject: Re: [Boost-users] Replace icpx with icpc
Hi,
FWIW, same problem with 2021.3.0. It selects icpx not matter what, and then
fail compiling context despite he --without-context option...
lainm@jarvis:/work/alainm/install/boost_1_76_0$ ./b2 Performing configuration
checks
- default address-model : none (cached) [1]
- default architecture : none (cached) [1]
Building the Boost C++ Libraries.
- x86 : no (cached) [2]
- arm : no (cached) [2]
- mips1 : no (cached) [2]
- power : no (cached) [2]
- sparc : no (cached) [2]
error: No best alternative for libs/context/build/asm_sources
next alternative: required properties: <abi>aapcs <address-model>32
<architecture>arm <binary-format>elf <threading>multi <toolset>clang
not matched
and then will fail recognizing any C++ feature:
- C++11 mutex : no (cached) [2]
- lockfree boost::atomic_flag : no (cached) [2]
- has stat::st_mtim : no (cached) [2]
- has stat::st_mtimensec : no (cached) [2]
- has stat::st_mtimespec : no (cached) [2]
- has stat::st_birthtim : no (cached) [2]
- has stat::st_birthtimensec : no (cached) [2]
- has stat::st_birthtimespec : no (cached) [2]
- has statx : no (cached) [2]
- has statx syscall : no (cached) [2]
- cxx11_auto_declarations : no (cached) [2]
- cxx11_constexpr : no (cached) [2]
- cxx11_defaulted_functions : no (cached) [2]
- cxx11_final : no (cached) [2]
- cxx11_hdr_mutex : no (cached) [2]
- cxx11_hdr_tuple : no (cached) [2]
- cxx11_lambdas : no (cached) [2]
- cxx11_noexcept : no (cached) [2]
- cxx11_nullptr : no (cached) [2]
- cxx11_rvalue_references : no (cached) [2]
- cxx11_template_aliases : no (cached) [2]
- cxx11_thread_local : no (cached) [2]
- cxx11_variadic_templates : no (cached) [2]
- cxx11_auto_declarations : no (cached) [3]
- cxx11_constexpr : no (cached) [3]
- cxx11_defaulted_functions : no (cached) [3]
- cxx11_final : no (cached) [3]
- cxx11_hdr_mutex : no (cached) [3]
- cxx11_hdr_tuple : no (cached) [3]
- cxx11_lambdas : no (cached) [3]
etc...
Thanks
----
Alain Miniussi
DSI, Pôles Calcul et Genie Log.
Observatoire de la Côte d'Azur
Tél. : +33492003009 (Mont-Gros)
+33483618544 (Sophia Antipolis)
+33609650665
----- On 31 Juil 21, at 22:46, Borchert, Christopher B ERDC-RDE-ITL-MS CIV via
Boost-users boost-users@lists.boost.org wrote:
> I'm trying to build Boost 1.76 from source on SLES 15 using Intel
> 19.1.3.304 (and GCC 10.2.0 underneath). Simply, how to I get b2 not to
> use icpx? With icpc it builds but icpx gives
>
> ./b2 toolset=intel-linux
> icpx: error while loading shared libraries: libimf.so: cannot open
> shared object
> file: No such file or directory
>
> I've tried everything and resorted to altering $PATH to remove icpx,
> which is how I know that's the problem.
>
> Thanks,
> Chris
> _______________________________________________
> Boost-users mailing list
> Boost-users@lists.boost.org
> Blockedhttps://lists.boost.org/mailman/listinfo.cgi/boost-usersBlocked
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
https://lists.boost.org/mailman/listinfo.cgi/boost-users
