On Wed, 5 Sep 2012, Basile Starynkevitch wrote: > Well, to take a concrete example, I don't understand well how on > Debian/Sid can I know that the gcc-4.6-plugin-dev package is for > x86-64-unknown-linux. the files provided by that package don't tell > much.
The plugin itself shouldn't need to know or care about that (remember, the same plugin, built for a different host but the same target, should behave identically). And to the extent the plugin cares about e.g. host C library features, I think the expectation would be to use autoconf to detect those. > Or are you suggesting I should use the packaging metainformation? I am suggesting that the logical concepts plugins should care about do not include the host triplet at all. (They might include "how do I execute compiled code", but I'd think that would best be externally configured in some way.) Whatever the problem is, I don't think using a host triplet in a plugin is the right solution. But you, as a human being, wanting to know the configuration of a particular distribution package, should indeed examine the metadata of that package (or of your installation as a whole). -- Joseph S. Myers jos...@codesourcery.com
