I have realised that mpir is as far as I am aware the only project I have compiled so far that uses configure. At least the only one that has caused issues thus bringing it to my attention.
It may be an issue with msys and sh.exe although the last isssue (cannot determine how to define a 32-bit word) appears to be a compiler issue. its probably the test thats bad With the python detection issue. I realised that configure may be using the exit value the opposite to the way I assumed. i.e. exit code 0 is actually a successful test. Is that the case? If so I need to workout why python detection fails. On 3 May 2013 00:09, Bill Hart <goodwillh...@googlemail.com> wrote: > I'm afraid I haven't seen this before. If it is randomly doing this, then > there must be something wrong with the environment. Sorry I don't think I > have any specific advice. > > Bill. > > > On 2 May 2013 14:33, gmail <cham...@gmail.com> wrote: > >> >> When attempting to configure using the latest mingw install i get the >> following error... >> >> checking for assembler local label prefix... L >> checking for assembler byte directive... .byte >> checking how to define a 32-bit word... configure: error: cannot >> determine how to define a 32-bit word >> >> At that point configure quits >> >> >> DC >> >> >> On 02/05/2013 9:54 PM, Bill Hart wrote: >> >> Hi, >> >> is this using Cygwin, MinGW or MSVC? >> >> If you are getting random hangs, it could be due to an antivirus >> program or an old version of MinGW. >> >> Bill. >> >> >> On 2 May 2013 12:51, developerchris <cham...@gmail.com> wrote: >> >>> >>> The main error is a particularly odd one >>> >>> when using the emerge system to compile mpir on windows xp it just hangs >>> at seemingly random places while configuring yasm >>> >>> Sometimes it will fail complaining that python is too low a version. it >>> requires > 2.4 and my version is only 3.3 >>> >>> I am pretty sure the fault is the test in yasm\configure >>> >>> line 7890 and line 7921 declare sys.exit(sys.hexversion < minverhex) >>> >>> I think that needs to be sys.exit(sys.hexversion > minverhex) >>> >>> Not sure how this could ever compile with that bad test in there? >>> >>> Still that is fixable. the strange hangs leave me lost I dont know where >>> to look. the various make logs don't shed any light on the issue at all. >>> >>> It just hung once again at this point >>> >>> config.status: linking >>> /r/build/win32libs/mpir-20120201/work/mpir-2.5.0/mpn/generic/mod_1_2.c to >>> mpn/mod_1_2.c >>> >>> config log shows >>> config.status:1647: linking >>> /r/build/win32libs/mpir-20120201/work/mpir-2.5.0/mpn/generic/mod_1_2.c to >>> mpn/mod_1_2.c >>> >>> This is after linking many files. >>> >>> more often it will hang at configure: creating ./config.status >>> >>> When it hangs I have to kill the shell its running in ^C does not work >>> >>> Any ideas what I can do to track this issue down? >>> >>> >>> >>> >>> DC >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "mpir-devel" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to mpir-devel+unsubscr...@googlegroups.com. >>> To post to this group, send email to mpir-devel@googlegroups.com. >>> Visit this group at http://groups.google.com/group/mpir-devel?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "mpir-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mpir-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to mpir-devel@googlegroups.com. >> Visit this group at http://groups.google.com/group/mpir-devel?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mpir-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mpir-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to mpir-devel@googlegroups.com. >> Visit this group at http://groups.google.com/group/mpir-devel?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mpir-devel+unsubscr...@googlegroups.com. > To post to this group, send email to mpir-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/mpir-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
