Boost failed updating 2 targets
Alternatively, set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost. Performing configuration checks - has_icu builds : no Component configuration: - date_time : building - filesystem : building - graph : not building - graph_parallel : not building - iostreams : building - math : not building - mpi : not building - program_options : building - python : not building - random : not building - regex : building - serialization : building - signals : not building - system : building - test : not building - thread : building - wave : not building ...patience... Global symbol "$directory" requires explicit package name at /software/bcl2fastq/bcl2fastq-1.8.4/lib/bcl2fastq-1.8.4/perl/Casava/Alignment/line 753.
If you find this article useful, please let me know. lm/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/query ld: library not found for -lboost_thread clang: error: linker command failed with exit code 1 (use -v to see invocation) // Additional error messages... mert/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/vocabulary_test ld: library not found for -lboost_thread clang: error: linker command failed with exit code 1 (use -v to see invocation) "g " -o "mert/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/vocabulary_test" "mert/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/Vocabulary Test.o" "mert/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/libmert_lib.a" -lboost_unit_test_framework -llzma -lbz2 -ldl -lboost_system -lz -lboost_thread -lm -liconv -g -Wl,-dead_strip -no_dead_strip_inits_and_terms ...failed mert/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/vocabulary_test... You MUST do 3 things before sending to the mailing list: 1. I asked on the mailing list, and their advice was to do some clean installations because it’s obvious something was broken here, especially with boost.
It assigns the symbolic name “/libs/number” to the project in the “number” subdirectory.
It’s overkill for such a simple example, but this abstraction means our test project will have no dependency on the exact location of the number library.
Still now the correct address-model=[32|64] must be specified, but you're right - it makes sense to combine the code for the architectures, so I updated the PKGBUILD accordingly.
You may already have a working copy of the Boost C libraries.
Search for boost failed updating 2 targets:
In order to help, I’ve put together a simple tutorial that combines Boost. If not, you can refer to my earlier post or the Boost Getting Started Guide. Build requires two extra packages: The bjam package installs Boost’s variant of the jam build tool, whereas the boost-build package installs a set of bjam configurations that form the actual Boost. If you’re not lucky enough to have a boost-build package or equivalent, you can get a pre-built bjam binary and sources for Boost. Once you have everything set up, you should be able to run bjam –version and see similar to the following output: If you don’t see details of the Boost. Build’s support for multiple projects in a single tree, I split my sample code into two pieces: a simple library, and the test code itself.