From: Neil Gower Newsgroups: comp.os.msdos.djgpp Subject: Re: using configure with VC6? Date: Wed, 26 Jun 2002 17:07:43 -0400 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <3D1A2D1F.9050308@inago.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse AT supernews DOT com Lines: 74 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli and Hans, Thanks for your suggestions, I really appreciate your help. Some good and some bad results. I had a look in config.log, and it said: -- start from config.log -- configure:1091: checking whether the C compiler (cl ) works configure:1107: cl -o conftest conftest.c 1>&5 Microsoft (R) 32-bit C/C++ Optim #line 1102 "configure" #include "confdefs.h" main(){return(0);} rp 1984-1998. All rights reserved. conftest.c Microsoft (R) Incremental Linker Version 6.00.8447 Copyright (C) Microsoft Corp 1992-1998. All rights reserved. /out:conftest.exe /out:conftest.exe conftest.obj configure: failed program was: -- end from config.log -- I did a quick test, and the cl output is consistent with a successful build, except that it would generate conftest.exe, not conftest. So I hacked up the configure script and set ac_exeext=.exe (is there a proper way to do this?). That got me a little further. After I set LD=cl in my environment, I got as far as: -- start from console -- checking command to parse nm output... failed checking for dlfcn.h... #line 1 "conftest.c" #line 2042 "configure" #line 1 "confdefs.h" #line 2043 "configure" no checking for ranlib... no checking for strip... no checking for objdir... .libs checking for cl option to produce PIC... none checking if cl static flag works... yes checking if cl supports -c -o file.obj... -- end from console -- At that point, configure just stopped, apparently locked up. Couldn't ^C or anything. When I re-ran configure, it miraculously completed, though there were several errors surrounding creating and deleting the conftest directory (which was left over from the locked up run). I ran it one more time, and configure seemed to run cleanly. Does that mean everything should be good to build? So now I've got a makefile (hurray!), which doesn't work with nmake (sigh). However, GNU make works just fine. Now it looks like just problems with the code... nothing to do with DJGPP I think. A few lessons learned for dealing with VC6 and configure: * don't forget to run VCVARS32.bat first * set CC=cl * set LD=cl * cl seems to deal with Unix style compiler options okay (e.g. -E and /E both work)... how unusually compatible of an MS product... ;-) Thanks again for all your help. Any feedback on the above is welcome, but I hope I'll be able to hobble on from here. ;-) Cheers, Neil.