The other "big" change we made was to make the library text's section non- executable , although I dont quite see how this could cause the error , but the early gcc's dont support it , I think. I'll look it up to try and see.
Jason On Thursday 18 November 2010 22:57:18 Jason wrote: > It's works with cygwin which is slightly older still , however cygnus do > patch it though.By default on linux both shared and static builds are > attempted , perhaps trying each one on it's own might resolve the issue. > ie > > --disable-shared --enable-static > and > --disable-static --enable-shared > > Jason > > On Thursday 18 November 2010 22:41:23 Bill Hart wrote: > > That same set of options with gcc 4.4.3 works fine on my x86_64 linux > > machine. Jeff's gcc is very old. Don't know if that's significant > > though. It technically should build. > > > > Bill. > > > > On 18 November 2010 22:29, Jason <ja...@njkfrudils.plus.com> wrote: > > > On Thursday 18 November 2010 20:17:03 Jeff Gilchrist wrote: > > >> Some rc2 tests. Here are the ones that passed: > > >> > > >> 1. Intel Xeon X5550 running Linux 64bit > > >> ./config.guess = nehalem-unknown-linux-gnu > > >> ICC v11.0 with --enable-cxx = All tests passed > > >> ICC v11.0 with --enable-cxx --enable-assert --enable-fat = All tests > > >> passed GCC v4.1.2 with --enable-cxx = All tests passed > > >> GCC v4.1.2 with --enable-cxx --enable-assert --enable-fat = All tests > > >> passed > > >> > > >> 2. Intel Xeon E5405 running Linux 64bit > > >> ./config.guess = penryn-unknown-linux-gnu > > >> ICC v11.0 with --enable-cxx = All tests passed > > >> ICC v11.0 with --enable-cxx --enable-assert --enable-fat = All tests > > >> passed GCC v4.1.2 with --enable-cxx = All tests passed > > >> GCC v4.1.2 with --enable-cxx --enable-assert --enable-fat = All tests > > >> passed > > >> > > >> 3. AMD Opteron 248 running Linux 64bit > > >> ./config.guess = k8-unknown-linux-gnu > > >> GCC 3.4.6 with --enable-cxx = All tests passed > > >> > > >> 4. Intel Core2 running cygwin32 (older version of cygwin) > > >> ./config.guess = core2-pc-cygwin > > >> GCC 3.4.4 with --enable-cxx = All tests passed > > >> > > >> 5. Intel Core2 running Windows Vista 32bit > > >> MS Visual Studio 2008 Express (pentium4 32bit project) = All tests > > >> passed > > >> > > >> > > >> Here is the one that failed: > > >> > > >> 1. AMD Opteron 248 running Linux 64bit > > >> ./config.guess = k8-unknown-linux-gnu > > >> GCC 3.4.6 with --enable-cxx --enable-assert --enable-fat = FAIL > > >> /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 > > > > > > I'm assuming case 3 is on the same machine as the failed case ? > > > > > > Did the previous mpir v2.1 fail with the same options ? > > > > > > Can you try it without the --enable-assert to see if it's some old > > > assertion getting in the way , and also perhaps without --enable-cxx to > > > see if it's the c++ being a problem. > > > Do you have another compiler on that system to try ? , in case it is > > > that particular compiler setup. > > > > > > You could try replacing mpn/x86_64/fat/fat_entry.asm with the version > > > from mpir v2.1 , as the file has changed , but only a little bit ! > > > > > > > > > Thanks > > > 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-de...@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-de...@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.
