From: Earnie B. <ear...@ya...> - 2001-03-23 15:46:01
|
Nicholas Lewin-Koh wrote: > > Hi, > I am going to whine a little bit, so let me preface this with the comment > that I have been using the mingw tool chain for about 3years now, and > truely appreciate never having had to buy M$VC++. Thank you, Now.. > > I have been following the discussion about mingw as a host, cygwin and the > mno-cygwin switch etc. My set up is as follows: > in C:/cygwin - all the usual stuff except perl, gcc, binutils (mostly > there for bash, groff, sed etc) > in c:/GNU I have mingw/ > with all the latest distributions from the source forge site. > > No if I download a new package from the net and I want to compile it my > dream would be to just type in my bash shell > > ./configure --host=mingw32; make; make install > Unless you've actually built GCC as a MinGW cross under Cygwin this won't work. You should instead do CC='gcc -mno-cygwin' ../configure in order to have autoconfiguration find the correct resources. This of course won't get rid of all of your problems but you'll be closer than you were before. > and go get a cup of coffee while it compiles. > You'll still have to set the cup down but not as often, hopefully. Earnie. P.S.: As a matter of practice you should never configure in the source directory unless the package is badly configured so as to force you to. Some packages will not correctly make if you do configure in the source directory. This is a GNU standard. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |