The BCL files are also more compact, requiring only 1 byte/base (B/b) as compared to QSEQ files which require about 2.5 B/b.In addition, the intensity files are also not transferred by default, so RTA output goes from 10 B/b to just 1 B/b.The new version does not compile, and the source of the problem is not clear to me. Boost 1.54 is getting fairly old so it wasn't tested using the newer versions of GCC. I'm using Boost 1.58 on Debian Testing and on windows msys2/ming64 without any issues other than the know boost polygon bug which still hasn't been fixed.I'm using clang as my primary compiler, and the absolutely latest packages available from the Arch Linux repo (in terms of OS config). Last working compilation (which I'm using atm) happened 3 weeks ago. Thank you kindly, Regards, Pete [code] [email protected] in ~/kicad- :make all [ 0%] Performing build step for 'boost' Performing configuration checks - 32-bit : no (cached) - 64-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) - zlib : yes (cached) - iconv (libc) : yes (cached) - icu : yes (cached) - has_icu builds : yes (cached) - zlib : yes (cached) Component configuration: - atomic : not building - chrono : not building - context : building - coroutine : not building - date_time : building - exception : not building - filesystem : building - graph : not building - graph_parallel : not building - iostreams : building - locale : building - log : not building - math : not building - mpi : not building - program_options : building - python : not building - random : not building - regex : building - serialization : not building - signals : not building - system : building - test : not building - thread : building - timer : not building - wave : not building ...patience... I have downloaded boost_1_54_0gz as it is a prerequisite for installing Top Hat. There will be a boost package (several in fact) available in the ubuntu package manager and using that is a lot easier than adding in external source libraries which aren't managed by your package manager.
It may still have successfully compiled and installed the parts of boost you need for Top Hat.Hello, I am trying to build Boost 1.55 on Windows with the instructions I found here: https://software.intel.com/en-us/articles/building-boost-with-intel-c-composer-xe-2013-on-windows-7 So after I do the bootstrap from the Intel cmd prompt, I do: D:\vs2013 projects\boost_1_55_0bjam toolset=intel address-model=32 I get a ton of errors like this: ------------------------------------------------------------------------------------------------------------- call "C:\Program Files (x86)\Intel\composer xe 2013 sp1\bin\intel64//iclvars .bat" nul icl @"bin.v2\libs\chrono\build\intel-win\debug\address-model-32\link-static\thre ading-multi\thread_rsp" ...failed compile-c-c bin.v2\libs\chrono\build\intel-win\debug\address-model-3 2\link-static\threading-multi\thread_..compile-c-c bin.v2\libs\chrono\build\intel-win\debug\address-model-32\link-sta tic\threading-multi\process_cpu_'"C:\Program Files (x86)\Intel\composer xe 2013 sp1\bin\intel64//iclvars.bat"' i s not recognized as an internal or external command, operable program or batch file.If you failed fewer targets (up to 5), you’re probably ok for hedge, but you might still want to install is a compiler tag that depends on the compiler with which you built boost. Check the contents of your boost library directory to find out what the correct tag is.