I have been having another failure pertaining to the GCC linker recently. I am receiving "multiple definition" errors after updating to a newer engine. As far as I can tell I think the reason for the test breaking is due to
Stephen's change back in February of last year to the native order module.
If I revert the engine to before that change was made, the library being built by GCC works just fine, so I don't think the "-Wl,--no-as-needed" will be enough for my case (although, I'm still not 100% convinced Boost.Build is at fault. I'm not familiar enough with the codebase of the project to prove otherwise).
Additionally, the Python port is still using some variant of the automatic sorting and does not use the native C module.
Aaron
