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 On Feb 29, 10:36 pm, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > gnani wrote: > > I read this link and your replies. I'm trying to make vim binary for > > NetBSD-3.0 from CYGWIN_NT-5.0 system. So, i tried cross compiling the > > vim. It was not successful initially. Then I tried with your patches > > for configure.in and configure scripts. I get the following error > > messages while configuring. > > ------- > > checking for strip... strip... configure: error: failed to compile > > test program > > configure: error: cannot compile a simple program, check CC and > > CFLAGS > > (cross compiling doesn't work) > > ------ > > This is what my configure parameters and I executed like below. > > > ./configure --build=i686-pc-cygwin --host=i386-unknown-netbsdelf3.0 -- > > target=i386-unknown-netbsdelf3.0 --with-tlib=ncurses > > > but I haven't set any other environment variables like you said > > already. > > > If you could give me some solution to get my expected binary, it will > > be great helpful? > > Thanks alot in advance. > > > Regards, > > Gnani. > > The way it is distributed with Vim, configure runs by making some assumptions > about the system upon which it is installed, and testing them by compiling > test programs. Whether each test program can be compiled, linked, and/or run, > and what the exit return is in each case, gives it the data it needs. However, > this means that configure must be used on the same system where the compiled > Vim will ultimately be run. > > If you want to cross-compile Vim, you will have to tell configure explicitly > everything it needs to know about the target system -- it cannot test it by > running test programs. This means that you will have to patch the configure > script so that it doesn't try to run test programs on the target system, _and_ > give it a lot of info -- all the info it would normally have found out by > running the tests you're suppressing. > > Alternately, you can either: > > a) compile on the target system itself, using configure as implicitly called > by the top-level Makefile, if it is a Unix-like system. That Makefile calls > src/Makefile, which has some notes about BSD, NetBSD and FreeBSD, so I suppose > you can use it without too many changes if you can afford to compile on NetBSD > for NetBSD. > > b) write a different makefile in the src subdirectory, like the several ones > which have been written for Windows compilers, and give it by hand (e.g. by > environment variables) all the installation-dependent info they need. > > Best regards, > Tony. > -- > The use of COBOL cripples the mind; its teaching should, therefore, be > regarded as a criminal offense. > -- E. W. Dijkstra > Issuing dogmatic statements, even anathemata, about all and sundry programming > languages, as if one were the Pope of Programming, is a far worse > mind-crippling criminal offense. We've got enough trouble with one Pope as it > is. > -- A. J. Mechelynck- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
