first iceadtea cross-compile patch: disable sanity checks
Andrew John Hughes
gnu_andrew at member.fsf.org
Tue Mar 31 04:33:51 PDT 2009
2009/3/28 Robert Schuster <theBohemian at gmx.net>:
> Hi Matthew,
> Matthew Flaschen schrieb:
>> I definitely think it should be optional, as you suggest in a comment.
>> Otherwise, you're making things more difficult for someone building the
>> code for the first time (or building on a new system).
> Please let me know if it is OK that way.
> There is one thing I would like to have but I don't know how to do it.
> Autoconf already checks whether one is cross-compiling:
> configure:3182: checking whether we are cross compiling
> configure:3184: result: yes
> In which variable is this result stored and when can I retrieve the
> value for sure?
> I want to implement the following algorithm in configure.ac:
> if (cross-compiling)
> disable sanity checks by default
> else if (--disable-sanity-checks was given)
> disable sanity checks
> do sanity check
> I only have the last part so far but the proposed automatism would be
> useful, since some of the sanity checks really can't be done when
> cross-compiling. Well, except if your host can run the target's binaries.
I see cross_compiling was adopted. This is set when host is specifed:
Can we actually have --disable-sanity-checks rather than
AC_MSG_CHECKING(whether to disable sanity checks)
[Disable sanity checks run by the OpenJDK build which
AM_CONDITIONAL([DISABLE_SANITY_CHECKS], [test x$DISABLE_SANITY_CHECKS = xyes])
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev