gnani wrote:
> Hello,
>
> I executed the vim configure for my cross compiling for NetBSD with
> all your patches (configure& configure.in). Configure completes
> properly. But by default, it takes my local GCC for making the target
> binary when i "make". And it generates only vim.exe file. Removing
> ".EXE" extension type from Makefile also didn't work out. It still
> generates the vim.exe.
> So in Makefile i just replaced "CC=GCC" with my NetBSD cross compile
> gcc path. Now it list out lot of errors when i "make".
>
> So exported the CC with my cross compile gcc path, in environment.
> making configure itself gives the following error:
>
> "checking for C compiler default output file name... configure: error:
> C compiler
> cannot create executables
> See `config.log' for more details."
>
> In this case, how should i use my cross compile gcc? Whether should be
> used in config.mk or should be exported like I said? But both the
> cases are not successful. What should i do now?
>
> Could you please give me some idea?
>
> Thanks& Regards,
> Gnani
You will probably have to modify the configure some more, so that:
- configure should never try to run gcc (neither the Cygwin-unix one,
the Cygwin-Windows cross-compiler, nor the Cygwin-BSD cross-compiler).
The only reason configure would try to run gcc is to check what kind of
software is installed on the target system (where the vim you'll compile
will have to run), but of course it cannopt run BSD programs, so any
such attempt is pointless.
- configure should also not try to check for the presence of software
such as include files or libraries, etc., because they could quite well
be present on the target system and not on the source system, or
vice-versa, or present in both but at a different place in the directory
tree, or with a different version. Here again, such checks are pointless
for a cross-compiler, unless you can install a mirror image of the
target system "chroot" on the source system. But in that case you may
want to replace the target gcc (and maybe also the target perl etc.) by
something like
#!/bin/sh
echo 'Error: trying to run software on the wrong machine'
return 255
- You will have to set up all the defines (HAVE_something etc.)
according to how the software works on your BSD system. You may have to
extensively edit auto/config.mk (or something) by hand after running
configure (or checking what it would do) to set up the defines
corresponding to your --with-features=something, --enable-xxxxinterp, etc.
Do you really not have a system running the same software as the target
system, where you could run configure and make? IMHO it would be
infinitely less problematic than trying to compile NetBSD software on a
Cygwin (or Windows) machine.
Best regards,
Tony.
--
God is a polytheist.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
