On Saturday 03 December 2011 23:49:09 Jason wrote: > On Saturday 03 December 2011 22:46:46 kcrisman wrote: > > > > > > > On Dec 3, 1:08 pm, kcrisman <kcris...@gmail.com> wrote: > > > > >> I have a repeatable failure. This is presumably due to the MPIR > > > > >> upgrade in 4.8.alpha0, > > > > >> seehttp://trac.sagemath.org/sage_trac/ticket/8664, > > > > > > > > Ah, I'm pretty sure yes. > > > > > > > >> configure: error: cannot build both static and DLL, since mpir.h is > > > > >> different for each. > > > > >> Use "--disable-static --enable-shared" to build just a DLL. > > > > >> Error configuring MPIR. (See above for the options passed to it.) > > > > > > This has always been the case for all windows systems , ie MSVC , cygwin > > > , MSYS , and even interex. > > > I don't think it's possible to make mpir.h independent of dll vs static > > > builds, it basically has to be done in the makefile/build solution > > > > > > > Thanks. Cactus on mpir-devel also commented: > > > > "I can only comment on the MSVC Windows build, for which I believe > > mpir.h is > > identical DLL and static library builds. To double check this I have > > just > > built both and compared the two mpir.h files that were generated. > > In fact mpir.h is now identical for win32 and x64 builds as well since > > I > > changed this recently to avoid any differences because an increasing > > number > > of people were trying to compile MPIR with the wrong version. > > Brian " > > > > If you (or anyone from sage-devel) have any specific tips on exactly > > where in the makefile or spkg-install this might be fixed, please > > comment on http://trac.sagemath.org/sage_trac/ticket/12115, where we > > are tracking this, or here. > > > > Also, just FYI, just bypassing this doesn't fix all our Cygwin > > problems - see the ticket above, again. > > > > Making all in yasm > > make[4]: Entering directory `/home/Administrator/sage-4.8.alpha3/spkg/ > > build/mpir-2.1.3.p8/src/yasm' > > gcc -std=gnu99 -I. -c -o genperf.o `test -f tools/genperf/genperf.c > > || echo './'`tools/genperf/genperf.c > > <snip> > > gcc -std=gnu99 -I. -c -o re2c-parser.o `test -f tools/re2c/parser.c > > || echo './'`tools/re2c/parser.c > > Makefile:3665: recipe for target `re2c-parser.o' failed > > make[4]: *** [re2c-parser.o] Error 1 > > make[4]: Leaving directory `/home/Administrator/sage-4.8.alpha3/spkg/ > > build/mpir-2.1.3.p8/src/yasm' > > Makefile:772: recipe for target `all-recursive' failed > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory `/home/Administrator/sage-4.8.alpha3/spkg/ > > build/mpir-2.1.3.p8/src' > > Makefile:603: recipe for target `all' failed > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/home/Administrator/sage-4.8.alpha3/spkg/ > > build/mpir-2.1.3.p8/src' > > Error building MPIR. > > > > This look like yasm is failing because your doing a parallel build , it's a > known problem and has been reported at least a year ago , it only seems to > effect cygwin , > a workaround is to build yasm first with just make and then build mpir with > make -j > > Jason > >
it's been fixed it appears see http://tortall.lighthouseapp.com/projects/78676/changesets/2bd66514b6b100887c19d8598da38347b3cff4 We should upgrade yasm in mpir to this for mpir-2.5 , which although delayed , I hope to get out next week, I've almost done all the tuning , just power7 to do , and some docs , and then our tests Jason -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
