On Fri, Sep 04, 2015 at 09:18:39PM +0200, Bram Moolenaar wrote: > James McCoy wrote: > > Because $CC is the compiler for the target system, not the native system. > > sjiscorr needs to be built by the native compiler, so it can be run to > > generate ja.sjis.po. > > > > It would probably be better to have something like: > > > > CC_FOR_BUILD ?= $(CC) > > > > and then use $(CC_FOR_BUILD) to build anything that needs to run during > > the build. > > Well, normally you would build the local binary first, before doing the > cross-compile build. That works, right?
Maybe it works, maybe not. How do I as someone new to Vim know what needs to be built using the native binary vs not? How am I supposed to make it so when I then cross-compile, the original failure seen here doesn't happen again? Why can't I just run “./configure --build=amd64-linux-gnu --host=aarch64-linux-gnu && make” and let the build infrastructure handle that for me? That's why configure has those flags. The autoconf-archive[0] even has a macro[1] to handle setting CC_FOR_BUILD for you. [0]: https://savannah.gnu.org/projects/autoconf-archive/ [1]: https://www.gnu.org/software/autoconf-archive/ax_cc_for_build.html Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]> -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
