On Aug 24, 2009, at 6:07 PM, Nils Bruin wrote:
> > On Aug 24, 4:51 pm, Jason Moxham <ja...@njkfrudils.plus.com> wrote: > >> To me 1) sounds like the best option, if ecl links with it own >> static version >> of gmp , then as long as we aren't leaking any symbols everything >> should just >> work . We are leaking some symbols though , some by accident , and >> some on >> purpose for testing/tuning, would have to have a closer look to >> see how many >> and what they exactly are , and how easy it is to "switch them >> off" for a >> local ecl static build. > > OK, let's make this a bit more concrete. I think the following line > gets executed during the ecl build in order to product libecl.so: > > gcc -o "/usr/local/sage/4.1.1/spkg/build/ecl-9.4.1/src/build/ > libecl.so" -L"/usr/local/sage/4.1.1/spkg/build/ecl-9.4.1/src/build/" > "c/main.o" "c/all_symbols2.o" "liblsp.a" "libeclmin.a" -shared -L/ > usr/ > local/sage/4.1.1/local/lib -L/usr/local/sage/4.1.1/local/lib -Wl,- > soname,libecl.so.9.4 -ldl -lm -lgc -lgmp > > and it results in a libecl.so that dynamically links to libgmp.so. How > do we change this line to produce a libecl.so that has the gmp library > privately inside? I think you can do -Wl,-Bstatic -lgmp at the end. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
