> (Dependencies on native or not are a bad idea. It's much better > always to do the same thing for a GNU/Linux target - or any other > target that can also be native - than to do things differently > depending on whether the same target is native or cross.)
Agreed. When we have a staged build directory, with all the libs that gcc + deps need in one canonical place, named coherently and consistently, built with proper deps, then we can use link tests. Till then, we bite it, avoid, and hard-code the minimum amount necessary. It's not optimum, but it's well established procedure. Let's not change this at random, on a per-port basis. Or, if we do, let's have a plan and communicate it clearly, with a full transition by all the runtime libs. Haphazardly breaking stuff is weak. -benjamin
