On Tuesday 15 February 2011 11:37:08 Cactus wrote: > On Feb 15, 11:20 am, "jason" <ja...@njkfrudils.plus.com> wrote: > > Hi > > > > I appear to of misunderstood you , after configure which you have done , > > type make and then make check > > > > Jason > > > > > > > > > > > > > > > > ----- Original Message ----- > > From: "Cactus" <rieman...@gmail.com> > > To: "mpir-devel" <mpir-devel@googlegroups.com> > > Sent: Tuesday, February 15, 2011 11:08 AM > > Subject: [mpir-devel] Re: MinGW64 > > > > 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 > > athttp://groups.google.com/group/mpir-devel?hl=en. > > Its not your problem Jason - you have to treat me as a complete novice > in this build environment I'm afraid. > > The make goes fine until: > > libtool: compile: x86_64-w64-mingw32-gcc.exe -std=gnu99 - > DHAVE_CONFIG_H -I. -I. > . -D__GMP_WITHIN_GMP -I.. -DOPERATION_divisible_p -O2 -m64 - > march=core2 -mtune=c > ore2 -c divisible_p.c -o divisible_p.o > divisible_p.c: In function '__gmpn_divisible_p': > divisible_p.c:76:3: error: 'TMP_DECL' undeclared (first use in this > function) > divisible_p.c:76:3: note: each undeclared identifier is reported only > once for e > ach function it appears in > divisible_p.c:122:4: error: 'SIZEOF_MP_LIMB_T' undeclared (first use > in this fun > ction) > divisible_p.c:141:3: error: 'TMP_MARK' undeclared (first use in this > function) > divisible_p.c:143:3: warning: implicit declaration of function > 'TMP_ALLOC' > divisible_p.c:143:8: warning: cast to pointer from integer of > different size > divisible_p.c:154:4: error: 'TMP_FREE' undeclared (first use in this > function) > make[2]: *** [divisible_p.lo] Error 1 > make[2]: Leaving directory `/usr/home/mpir/mpn' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/home/mpir' > make: *** [all] Error 2 > > It also seems to think my machine is a core2 system when in fact its > nehalem (i7) > > Any ideas? > > Brian
The march=core2 compiler option is normal , gcc has no option yet for the nehalem. Those undeclared MACROS come from gmp-impl.h , I assume it must be there otherwise you would of got an error when the file tried to include it , it's not an empty file is it? Could you post the whole output form configure and make and the file config.h config.log cheers Jason -- 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.
