Date: Fri, 28 Apr 2000 04:30:26 -0700 (PDT)
From: Mo DeJong <[EMAIL PROTECTED]>
Perhaps this is a stupid idea, but what about some kind of
config.compare script that takes two arguments (the $host and the $build)
and figures out if the two are "really the same" or if a cross compile
is in order. There are always going to be all kinds of wacky combinations
where if test "$host" != "$build" is just not going to cut it. Why don't
we put these info a config.compare script that can be improved over time?
It's really hard to write such a script, because you can't tell what
matters and what doesn't. Some code cares about the exact version of
the operating system (e.g., hpux10.20 vs. hpux 10.6). Some code does
not. What should config.compare do in such a case?
However, I said similar things about config.guess before Per Bothner
wrote it and proved me wrong. If you think config.compare can be
written, go ahead.
More to the point, perhaps, is that I don't think writing
config.compare will help in real situations. I think it will only
help in theoretical situations.
It's worth remembering that practically nobody builds with a
cross-compiler, and those who do need to know what they are doing at a
pretty deep level in order to succeed. Just specifying --host and
--build is not enough; you need to build a correct and complete
cross-compilation environment first. (That looks easy at Cygnus
because others have done the hard work.)
Ian
