On Wed, 20 Jul 2005, Dan Fandrich wrote:

> On Wed, Jul 20, 2005 at 03:07:09PM +0800, Tim Sneddon wrote:
> > >but it will be the executable that bails instead of configure in
> > >that case. Better to force the user to "deal with it" at
> > >configure time by bailing then.
> >
> > How can the user "deal with it" at configure time if they are
> > cross-compiling? In some cases, like library dependencies I can
> > understand it (how else is it going to compile?). However, if you
> > are referencing a device specific to the target system, then there
> > is no way of checking it. It will most probably not (as in this
> > case) exist on the build system.
>
> The user deals with it at configure time by giving the --with-random=
> option.

ah, i didn't realize that that would override the normal checking
(that is what it's doing, right?). if that's the case, then i can see
that being the way to "deal" with issues like this related to
cross-compiling.

rday
Received on 2005-07-20