On Sunday, 10 June 2012 17:15:09 UTC+1, Jason Moxham wrote:
>
>
> > Hi 
> > 
> > I figured out what going on here , basically configure is failing to 
> > populate config.h with the required 
> > #define HAVE_NATIVE_mpn_addmul_2 1 
> > and all the others , it has always done this on mingw64 but because of 
> > the way the C file redc_2 uses addmul_2 it now causes a problem.A 
> > quick fix is to delete the lines in the mpn/generic/redc_2.c file 
> > where it trys to redefine addmul_2 
> > 
> > I don't know why configure fails to populate config.h , it manages to 
> > do the sym links 
>
> Doesn't configure scan the assembler files looking for PROLOGUE(symbol) 
> to determine whether to include HAVE_NATIVE_symbol in config.h? 
>
> If so, configure won't pick up the symbols because the Windows assembler 
> files don't have any PROLOGUE macros.   
>
> But this doesn't explain how it ever worked! 
>
>     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 at 
> http://groups.google.com/group/mpir-devel?hl=en. 
>
> ============================================================================= 
>
>
> yeah it scans them for PROLOGUE and GLOBAL_FUNC , but the sym links come 
> from the file names , no idea why mingw64 should be different , i'm even 
> using the same msys , and the compiler is not used here. I do some file 
> name transformation but that is the last thing configure does , at the 
> moment I'm stumped , have to let it stew for a while 

 
================

> But if the PROLOGUE and/or GLOBAL_FUNC macros are needed in assembler 
> files in order to generate the HAVE_NATIVE_symbol defines in config.h, 
> isn't their absence explained by the lack of these macros in my Windows 
> assembler files?


       Brian
 

 

>  
>

 

> Jason 
>

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/mpir-devel/-/nuUwEeDf2rkJ.
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.

Reply via email to