I ran b2 with the -d+2 command and redirected the output to a file
This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file.
This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file.
When you join a log file to an email, please compress it. Your 1Mb file becomes 29kb with just bzip2 -9 but anything else would do the same. Did you discover anything interesting in the log? F
Is there something wrong with the configuration? I see linker and compiler errors, but for the latter it's only for GetModuleA. How do I get it to find those things?
________________________________
From: Fr?d?ric
This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file.
When you join a log file to an email, please compress it. Your 1Mb file becomes 29kb with just bzip2 -9 but anything else would do the same. Did you discover anything interesting in the log? F
From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Osman Zakir via Boost-users Sent: 03 January 2019 22:27 To: boost-users@lists.boost.org Cc: Osman Zakir Subject: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file. Well this looks quite encouraging - in that most of the key libraries are built OK. Well done for exploring off the end of the known universe! You can see a complete list of successes by looking your /lib/ folder. A few more Wno- items would reduce clutter in the log file. You may probably find that you can use what you have to get some or all of your applications going (partly because so much of Boost is header only). Worth a try to size the scale of remaining problems? So congratulations for making a big step forward (despite the size of the log file ;-) If you decide that you dont need the failing libraries, you can get a clean build by adding-- without_some_library for example --without-python ...
b2 -a will try to build everything from scratch.
(If you want a completely clean re-build, you can, are from time to time should, delete the whole of the folder bin.v2 before running b2 with all your options - most conveniently in a .bat file). Sadly I have no idea on individual failures, but I fear you will have to raise a query with each failing library maintainer (on this list) to find what is missing to build the failing libraries. For example: You are not alone is finding that __imp_CryptEnumProvidersA is missing http://boost.2283326.n4.nabble.com/boost-1-19-0-fails-to-build-random-using-... I think that this should be provided by Microsoft Strong Cryptographic Provider https://docs.microsoft.com/en-us/windows/desktop/seccrypto/microsoft-enhance... is wincrypt.h inaccessible? Or is there a .dll that you need to link? Sadly Microsoft seem not to provide an index of all these __imp_ items. I've had to guess :-( Keep going! Paul PS 7-zip.org provides the most popular and convenient zipper. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
If I post here which libraries failed, and then show the log file again, will I get more help that way?
I passed arguments "--prefix=C:/Boost" and "--build-dir=C:/Boost_Build", and I have no Boost directory right now even after the build completed. And I had that same "failed updating 44 targets" error again too. But I do have .lib files for the following libraries in the stage/lib directory in C:/boost_1_69_0:
Atomic, Chrono, Container, Context, Contract, Coroutine, Date_time, Exception, Fiber, Filesystem, Graph, Iostreams, Locale, Math_c99 (including f and l ones), Math_tr1 (including f and l ones), Prg_exec_monitor, Program_options, Python37, Random, Regex, Serialization, Stacktrace_noop, System, Text_exec_monitor, Thread, Timer, Type_erasure, Unit_test_framework, Wave, Wserialization.
I don't have shared libraries, though. But maybe I don't those anymore. I ran b2 without specifying anything other than "--layout=versioned" , "-d+2", and the prefix and build-dir flags. And directed the output to a log file like before. Though it could be that some of the .lib files for each of the libraries failed to build.
________________________________
From: Boost-users
b2 -a will try to build everything from scratch.
(If you want a completely clean re-build, you can, are from time to time should, delete the whole of the folder bin.v2 before running b2 with all your options - most conveniently in a .bat file). Sadly I have no idea on individual failures, but I fear you will have to raise a query with each failing library maintainer (on this list) to find what is missing to build the failing libraries. For example: You are not alone is finding that __imp_CryptEnumProvidersA is missing http://boost.2283326.n4.nabble.com/boost-1-19-0-fails-to-build-random-using-... I think that this should be provided by “Microsoft Strong Cryptographic Provider” https://docs.microsoft.com/en-us/windows/desktop/seccrypto/microsoft-enhance... is wincrypt.h inaccessible? Or is there a .dll that you need to link? Sadly Microsoft seem not to provide an index of all these __imp_ items. I've had to guess :-( Keep going! Paul PS 7-zip.org provides the most popular and convenient zipper. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830 _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
If you want shared libraries you need to specify “link=runtime” on the b2 command line. If you want the libraries to use shared runtime libraries you also need to include “runtime-link=shared”.
From: Osman Zakir via Boost-users
Sent: Saturday, January 5, 2019 9:02 AM
To: boost-users@lists.boost.org
Cc: Osman Zakir
Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
If I post here which libraries failed, and then show the log file again, will I get more help that way?
I passed arguments "--prefix=C:/Boost" and "--build-dir=C:/Boost_Build", and I have no Boost directory right now even after the build completed. And I had that same "failed updating 44 targets" error again too. But I do have .lib files for the following libraries in the stage/lib directory in C:/boost_1_69_0:
Atomic, Chrono, Container, Context, Contract, Coroutine, Date_time, Exception, Fiber, Filesystem, Graph, Iostreams, Locale, Math_c99 (including f and l ones), Math_tr1 (including f and l ones), Prg_exec_monitor, Program_options, Python37, Random, Regex, Serialization, Stacktrace_noop, System, Text_exec_monitor, Thread, Timer, Type_erasure, Unit_test_framework, Wave, Wserialization.
I don't have shared libraries, though. But maybe I don't those anymore. I ran b2 without specifying anything other than "--layout=versioned" , "-d+2", and the prefix and build-dir flags. And directed the output to a log file like before. Though it could be that some of the .lib files for each of the libraries failed to build.
--------------------------------------------------------------------------------
From: Boost-users
b2 -a will try to build everything from scratch.
(If you want a completely clean re-build, you can, are from time to time should, delete the whole of the folder bin.v2 before running b2 with all your options - most conveniently in a .bat file). Sadly I have no idea on individual failures, but I fear you will have to raise a query with each failing library maintainer (on this list) to find what is missing to build the failing libraries. For example: You are not alone is finding that __imp_CryptEnumProvidersA is missing http://boost.2283326.n4.nabble.com/boost-1-19-0-fails-to-build-random-using-... I think that this should be provided by “Microsoft Strong Cryptographic Provider” https://docs.microsoft.com/en-us/windows/desktop/seccrypto/microsoft-enhance... is wincrypt.h inaccessible? Or is there a .dll that you need to link? Sadly Microsoft seem not to provide an index of all these __imp_ items. I've had to guess :-( Keep going! Paul PS 7-zip.org provides the most popular and convenient zipper. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830 _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------------------------------- _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
I passed arguments "--prefix=C:/Boost" and "--build-dir=C:/Boost_Build", and I have no Boost directory right now even after the build completed. And I had that same "failed updating 44 targets" error again too. But I do have .lib files for the following libraries in the stage/lib directory in C:/boost_1_69_0:
I have never built boost for Windows using clang (I always build on Linux with mingw) and I see that it is not part of the regular tests: https://www.boost.org/development/tests/master/developer/summary.html Also I always add --without-python which is the first failed library you have, do you need it? I always add to b2: --layout=system --user-config=user-config.jam --without-mpi --without-python --without-context --without-coroutine link=static threading=multi runtime-link=shared target-os=windows threadapi=win32 variant=release With this, I have no failure and "...updated 15340 targets..." for 1.68.0. Good luck, F
On Sat, 5 Jan 2019 at 00:02, Osman Zakir via Boost-users < boost-users@lists.boost.org> wrote:
If I post here which libraries failed, and then show the log file again, will I get more help that way?
I passed arguments "--prefix=C:/Boost" and "--build-dir=C:/Boost_Build", and I have no Boost directory right now even after the build completed. And I had that same "failed updating 44 targets" error again too. But I do have .lib files for the following libraries in the stage/lib directory in C:/boost_1_69_0:
Atomic, Chrono, Container, Context, Contract, Coroutine, Date_time, Exception, Fiber, Filesystem, Graph, Iostreams, Locale, Math_c99 (including f and l ones), Math_tr1 (including f and l ones), Prg_exec_monitor, Program_options, Python37, Random, Regex, Serialization, Stacktrace_noop, System, Text_exec_monitor, Thread, Timer, Type_erasure, Unit_test_framework, Wave, Wserialization.
Your .\b2 command should be finished off by "install", then you'll get in C:\Boost (because that's what's your prefix a include, bin and a lib directory. I use the following b2 line: b2 -a -d+2 -j2 --toolset=clang-win --abbreviate-paths --prefix=%PREFIX% --build-dir=c:\boost-build --without-python --without-mpi --without-graph_parallel --disable-filesystem2 -o%HOME%\clang_log.log "-sZLIB_SOURCE=%HOME%\zlib-1.2.8" "-sBZIP2_SOURCE=%HOME%\bzip2-1.0.6" variant=debug variant=release threading=multi link=static runtime-link=static architecture=x86 address-model=64 instruction-set=haswell install I suggest that you, apart from the "install", add "--abbreviate-paths" as well, as some stuff might be failing due to excessively long path names [longer than 260 characters, which you on Win10 could fix at the OS-level]. There should be 3 stacktrace libs. degski -- *“If something cannot go on forever, it will stop" - Herbert Stein*
participants (5)
-
degski -
Frédéric -
Leo Carreon -
Osman Zakir -
Paul A. Bristow