On 8/16/10 3:17 PM, Philip Prindeville wrote:
Trying to cross-compile, but this breaks:
checking uint32_t is 32 bits... configure: error: could not compile program
using uint32_t.
Note that this error message is misleading. The program compiles just fine.
It simply won't run because it's built for the wrong architecture.
Not sure if this test is even useful: if you have a <stdint.h> file you should
trust it. So I would check for a program including this header file compiling, and
not bother actually running it.
Using the following patch. The assumption being that you have to trust your
<stdint.h> file by necessity, and if it's wrong then a whole cacastorm of
badness will be unleashed and you won't need vim's configure to tell you so.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
--- vim73/src/configure.in.orig 2010-08-13 08:15:17.000000000 -0600
+++ vim73/src/configure.in 2010-08-16 17:04:34.000000000 -0600
@@ -3180,7 +3180,7 @@ main() {
}],
AC_MSG_RESULT(ok),
AC_MSG_ERROR([WRONG! uint32_t not defined correctly.]),
-AC_MSG_ERROR([could not compile program using uint32_t.]))
+AC_MSG_RESULT([assuming ok]))
dnl Check for memmove() before bcopy(), makes memmove() be used when both are
dnl present, fixes problem with incompatibility between Solaris 2.4 and 2.5.
