It looks like the 1102c1107 < *-unknown) ---
> *-unknown | *-pc | *-apple) change to the default configfsf.sub is needed , this appears to be the cause of the change of the default behavour below , as the the same happend in cygwin , and I imagine on 32bit linux. The reason is all the extra cpus we distinguish , and this change is much easier than filling in all the cpu's all over the configfsf.guess/sub files I'll put a note in the devel directory , so like yasm , we can easily upgrade without wondering want to do :) ----- Original Message ----- From: jason To: [email protected] Sent: Saturday, August 28, 2010 9:59 AM Subject: [mpir-devel] mingw64 Hi I think I know why the mingw64 dll builds fail , for multiple functions files ie aors_err2_n.asm , in the MSVC build yasm emits both functions in a single "unit" , whereas under mingw64 we create two links add and sub versions (like we do for unix) , and also yasm still emits both functions , so we end up with two copys. The same must happen in the static build , but it doesn't seem to matter? I was planning to get rid of such complications ( or rather move them to development machines only , much like autotools generates Makefile.in) , a small script should easily take of it. For the t-locale test , is there no way that MSVC will pass it ? , if so I'll ifdef it out , with ! _MSC_VER , because under mingw I think I can get it to pass , it looks like the redefinition of localenv just needs a DECLSPEC The new configfsf.sub etc , seems to have changed the default behavor under mingw , so for the 64bit version you have to explictly tell it Jason -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
