I see , it's probably not possible the current way we implement the fat binarys where the real function addresses are not decided until runtime , I imagine we would need another level of indirection in them . i would suggest not using a fat binary but a static build of K8 or core2 builds which are the lowest common denominators.The x86_64 build is really the lowest but the current way we arrange the directory's means it's a slow build.
Jason ========================================================== This is the whole point. I want to link MPIR statically into my shared library. And it works if I do not use --enable-fat. But linking with fat library gives me error above. On Mon, Jul 9, 2012 at 4:42 PM, Jason Moxham <ja...@thecodecavern.co.uk>wrote: > Ah , it looks like your linking against libgmp.a not libgmp.so ? > > -- > 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 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.
