Enrico Weigelt wrote: > * Bill Gatliff <bgat@xxxxxxxxxxxxxxx> schrieb: > >> If the build system derives from autoconf, then a hacked-up >> config.cache (or equivalent command-line args) often solves >> problems for me. > > Only if you're working on *one specific* target for a long time. > I, for example, have to support lots of different targets, so your > approach does not work for me. I'm not exactly a one-specific-target kinda guy, either. I routinely move between MIPS, ARM, PPC and x86. Yea, that means target-specific config.cache files. But that works for me. > Ah, and it's not *solving* any problem, > just deferring it to some other day. If "solving" means helping the tool get the answer it needs, even when running in an environment/configuration it wasn't intended for, without breaking compatibility with everyone else out there still using the same tool, then I disagree. But hey, I never said you had to do it my way. :) b.g. -- Bill Gatliff bgat@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
