On 08/01/10 03:10, Philip A. Prindeville wrote:
Any chance of rebuilding the configure file that gets generated from
src/configure.in with a less ancient version of autoconf?
Say, 2.61 or more recent?
Prior to 2.61, autoconf was extremely cross-compile unfriendly...
Thanks,
-Philip
I believe that this "cross-compile unfriendliness" is intentional: the
idea is that configure tests a (large) number of features that may be
present on your computer, in most cases by generating test programs and
seeing if they compile without error, link without error, and possibly
even produce the desired output when run. It could of course not run
those test programs on a different architecture than that where they
were compiled and linked.
The alternative is to do as for non-Unix-like architectures: don't use
configure at all, but an ad-hoc makefile (there are already quite a
number of these, src/Make_*.mak) to which you would feed defines either
as command-line options or as environment variables. Then there is no
testing of your compiling / linking / running hardware and software
environment, and any variable settings must be supplied manually by
whoever runs the compile. See examples (including one for
"cross-compiling" a native-Windows Vim using Cygwin tools) in my HowTo
for Windows, http://users.skynet.be/antoine.mechelynck/vim/compile.htm
Best regards,
Tony.
--
"Star Wars is adolescent nonsense; Close Encounters is obscurantist
drivel; Star Trek can turn your brains to purée of bat guano; and the
greatest science fiction series of all time is Doctor Who! And I'll
take you all on, one-by-one or all in a bunch to back it up!"
-- Harlan Ellison
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
