On 01/07/2010 06:43 PM, Tony Mechelynck wrote: > 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.
Well, in our case, we're building on similar Linux releases, similar libraries, etc. I also note that a lot of other packages build (and run successfully) without run-time detection.
-- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
