On 22 May 2012 11:10, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > Within the Sage project, we discovered several issues with the > CPU/CFLAGS/MPN_PATH configuration code in MPIR-2.4.0. The code mostly > works well, but there are a few things I would like to change. > > I would also like to add a configuration option to build a "generic" > binary meaning one which would run on any CPU of a given architecture > (e.g. x86_64). It could still use assembly code, but only instructions > which exist on every CPU of a given architecture. >
I have decided that this is not practical. We currently need the processor detection to decide which broad assembly branch to use (x86, x86_64, etc). If you specify --build=generic-unknown-bulgarianwristwatch, it simply loses all the information it needs. The solution Jason suggested is much better: ./configure --build=$(./configfsf.guess) make make check make install This should work. If not we can look into why. (Note he mentioned it probably doesn't work on MinGW64, but there you only need to use --build=x86_64-unknown-pc.) Bill. > I would also like to reorganize the code to separate this configuration > code from the rest of MPIR. Within Sage, I would then use this for all > packages, not just MPIR. > > Does MPIR itself have any plans with this code? Is it likely you would > accept these changes that I'm proposing? > > > Jeroen. > > -- > 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. > > -- 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. For more options, visit https://groups.google.com/d/optout.
