From: <kao...@ve...> - 2007-09-04 18:25:04
|
Hello, Tuomo: In the MINGFW32 window, I did the following: 1) cd'ed to C:/msys/1.0/10/rt/src; 2) did the ./configure; 3) did "make install". Here are the MINGW32 window capture: ******************* myAccount@LPC30EESLAP91 ~ $ cd c:/msys/1.0/10/rt/src $ ./configure Configuring for a i686-pc-mingw32 host. Created "Makefile" in /10/rt/src using "mh-frag" Configuring etc... creating cache ../config.cache checking for a BSD compatible install... /bin/install -c updating cache ../config.cache creating ./config.status creating Makefile myAccount@LPC30EESLAP91 /10/rt/src $ make install /bin/sh ./mkinstalldirs /usr/local /usr/local mkdir /usr/local make[1]: Entering directory `/10/rt/src/etc' make[1]: Nothing to be done for `install'. make[1]: Leaving directory `/10/rt/src/etc' myAccount@LPC30EESLAP91 /10/rt/src **************************** Yet the same compilation error remains. I believe I still have some basic download-install problems, like missing a step somewhere. To answer one of your questions, I am trying to rebuild a couple of app-specific utility programs from Unix to Windows and later will run them under Windows. These utilities do not come with their own "configure" files. Under Unix, the build was done via ClearCase. Thanks for any possible insights. I am new to all these. Chuan From: Tuomo Latto <dj...@ik...> Date: 2007/09/02 Sun AM 07:27:52 CDT To: MSYS Discussion List <min...@li...> Subject: Re: [Mingw-msys] persistent compilation problem kao...@ve... wrote: > No, I did not do ./configure the utility. Could you tell me the directory where I should cd into before I do the ./configure? Just a thought. You said: "The purpose is to re build some Unix utility programs using makefiles." Many of the Unix utility programs, mainly the GNU ones (yes, I know "GNU is Not Unix"), use automake/autoconf so that one needs to configure the package to suit your system (they contain a shell script called configure). This then (re)creates the Makefile. Does the package(s) contain such a script? Anyway, let me make this clear: No one will be able to help you unless you provide some details. Despite what you may think, we don't read minds on this list. The usual checklist: 1) versions of all installed MSYS and MinGW packages 2) the location where you installed those 3) your path 4) anything else that could screw things up royally, like using Cygwin, GnuWin32 utilities, any stray libraries that might be picked up, include paths pointing to MSVC headers, etc. 5) what you're trying to do, for example: what are trying to build, are you building it as instructed accompanying documentation, what parameters are you using 6) is the utility ported to Windows (Windows is not POSIX) 7) the actual command lines you're using 8) do you have a minimal testcase? In your case, I know some of these may be omitted. However, you are still the only one who knows *anything* about your problem. -- Tuomo ... Mercifully free of the ravages of intelligence ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mingw-msys mailing list Min...@li... https://lists.sourceforge.net/lists/listinfo/mingw-msys |