-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yah, I'm aware of the warnings, they go away when --enable-auto-import is added.
I'm not going to add that flag to the Jamfile until I figure out exactly what
the warnings mean, and make sure adding that flag actually fixes the problem.
On Wed, 20 Oct 2010 13:28:59 +0000 (UTC)
Richard Webb
Bryce Lelbach
writes: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Phlipp, can I get the details of your mingw build? mingw throws a win32 stack overflow on my box when compiling libboost_serialization (and fails the compile).
I've been running the trunk regression tests with the mingw 4.5.1 build from http://tdm-gcc.tdragon.net/ -> seems more stable than other builds i've tried.
The regression test run last night failed but the current trunk version without fvisiblity-hidden is looking better, though there are a lot of
/////////// Info: resolving vtable for boost::archive::archive_exception by linking to __imp___ZTVN5boost7archive17archive_exceptionE (auto-import c:/mingw451/bin/../lib/gcc/mingw32/4.5.1/../../../../mingw32/bin/ld.exe: warning: auto-importing has been activated without --enable-auto-import specified on the command line. This should work unless it involves constant data structures referencing symbols from auto-imported DLLs.) ////////////
warnings from the tests.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
- -- Bryce Lelbach aka wash http://groups.google.com/group/ariel_devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEUEARECAAYFAky/CTAACgkQO/fqqIuE2t50bACg36a4WeafqIJ5IEn9GLnMDjKo EzcAl1RSka9OHQyR6PfbcmSOnfTGvIQ= =l76P -----END PGP SIGNATURE-----