On 01/25/2015 08:26 PM, Michael Caisse wrote:
On 01/25/2015 08:45 AM, Jürgen Hunold wrote:
Hi Volodya,
Am Sonntag, 25. Januar 2015, 18:09:39 schrieb Vladimir Prus:
It looks like something is explicitly requesting <address-model>64. I can't quite reproduce this on Linux, though. Could you run with --debug-building and grep the log to see where <address-model>64 first appears in build properties?
Those are the same symptoms as discussed last year. Your last comment on these issues can be found in:
http://lists.boost.org/boost-build/2014/12/27778.php
The final solution thus seems to always determine both <address-model> and <architecture>
The workaround for now is to either use
b2 --without-context --without-coroutine
in order to skip both libraries if not needed or explicitly run
b2 address-model=64 architecture=x86
and thus specify the defaults manually for all libraries. Note that this blows up build paths and leads to a doubled install size.
Yours,
Jürgen
Thank you Jürgen, your suggestion (--without-*) works.
Volodya, please let me know if there is something more I can provide. I have the --debug-building log if that is still helpful.
Michael, I think Jürgen's explanation is sufficient for me - I was tripped by the similarity with the endian problem that is now fixed. -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com