On Thursday 03 March 2011 16:06:14 Jeff Gilchrist wrote: > On Thu, Mar 3, 2011 at 11:02 AM, Jason <ja...@njkfrudils.plus.com> wrote: > > As we don't seem to have any regressions from mpir-2.2 , I think we can > > release 2.3 this evening. > > I'm running the test script now that I know it exists (thanks). Is > there a known issue with fat builds with GCC 3.4.x on K8 > (k8-unknown-linux-gnu)? This is what I get: > > PASSED CC=gcc CXX=g++ configure= > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat > --enable-assert --enable-alloca=debug > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat > --enable-assert --enable-alloca=debug --build=none-unknown-linux-gnu > FAILED CC=gcc CXX=g++ configure= --enable-fat > > The error: > > /usr/bin/ld: mpn/.libs/fat_entry.o: relocation R_X86_64_32S against > `_GLOBAL_OFFSET_TABLE_' can not be used when making a shared object; > recompile with -fPIC > mpn/.libs/fat_entry.o: could not read symbols: Bad value > collect2: ld returned 1 exit status > make[2]: *** [libmpir.la] Error 1
This also happens on mpir 2.2 and 2.1 see http://groups.google.com/group/mpir- devel/browse_thread/thread/b497c224ed505dc3/b72e01cf69c7b1fb?lnk=gst&q=_GLOBAL_OFFSET_TABLE_#b72e01cf69c7b1fb if you do gcc -v what is the exact output , perhaps when gcc was built some different option was used , we have quite a few gcc-3.4's on various machines and they all work fine , although some have broken c++ Jason -- 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.
