On Feb 15, 5:54 am, degski <deg...@gmail.com> wrote: > > my msys directory structure didn't have the home and user name part though > > Probably: > > mingw > mingw64 > msys > home > > 1.0 > <<<<<<<<<<<<<<<<<<< > Brian Gladman (added by msys) > mpir > > Cheers
Thanks for the further information - for some reason it was different on my system. I have just completely removed mingw/msys from my system (and deleted the associated directories) and then allowed the automated mingw installer to install mingw and msys with no intervention on my part so its default choices will apply. MSYS clearly states that mingw should be installed in a parallel folder but the automated installler puts msys inside the mingw directory so that I end up with: 15/02/2011 10:05 <DIR> . 15/02/2011 10:05 <DIR> .. 15/02/2011 10:03 <DIR> bin 15/02/2011 10:02 <DIR> doc 15/02/2011 10:03 <DIR> include 15/02/2011 10:03 <DIR> lib 15/02/2011 10:03 <DIR> libexec 15/02/2011 10:03 <DIR> mingw32 13/02/2011 18:08 <DIR> mingw64 15/02/2011 10:03 <DIR> msys 15/02/2011 10:03 <DIR> share 15/02/2011 09:59 18,244 unins000.dat 15/02/2011 09:57 756,062 unins000.exe 15/02/2011 09:59 <DIR> var The only intervention here on my part is the addition of the mingw64 directory holding the 64 bit tools. The msys home directory is at: Directory of C:\mingw\msys\1.0\home and contains: 15/02/2011 10:07 <DIR> . 15/02/2011 10:07 <DIR> .. 15/02/2011 10:05 <DIR> Brian Gladman 15/02/2011 10:50 <DIR> mpir The build with the command line: ./configure --enable-cxx CC=x86_64-w64-mingw32-gcc.exe NM=x86_64-w64- mingw32-nm.exe AR=x86_64-w64-mingw32-ar.exe CXX=x86_64-w64-mingw32-g+ +.exe behaves exactly as it has done before and terminates with: checking for iconv... no, consider installing GNU libiconv checking for GNU gettext in libintl... no checking whether to use NLS... no checking for GNU C Library... no configure: Checking for Python checking for a Python interpreter with version >= 2.4... none configure: WARNING: Python not found configure: WARNING: Could not find a suitable version of Python configure: creating ./config.status config.status: creating Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libyasm-stdint.h commands config.status: creating libyasm-stdint.h : _YASM_LIBYASM_STDINT_H config.status: libyasm-stdint.h is unchanged config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile Brian Gladman@MobileSlave /home/mpir $ I have now tried many different configurations, all of which fail in this same way :-( I get identical results on two different machines. What should happen after the above point in the build and where should the build outputs go? Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.