Yep, I have been investigating and that was the problem. "sudo sage - sh" did the trick.
However, I found that $LD_LIBRARY_PATH was being reset each time I typed "sudo bash"; moreover, in the Sage shell "sudo -E" (which, in theory, preserves environment, see http://www.gratisoft.us/sudo/man/1.8.0/sudo.man.html#e) just doesn't work _with this variable_. It seems strange, and I cannot tell if it is a problem with Sage, sudo or both. At least I have this workaround. Thanks! On Jun 9, 9:00 pm, Nils Bruin <[email protected]> wrote: > On Jun 9, 2:23 am, Juanlu_001 <[email protected]> wrote:> > juanlu@mercurius ~ $ sage -sh > [...] > > (sage subshell) mercurius:~ juanlu$ sudo easy_install pip > > python: error while loading shared libraries: libpython2.6.so.1.0: > > sudo probably resets a lot of environment for security reasons, so > part of the effect of "sage -sh" is undone. Probably > "sudo sage -sh" gets you better mileage (you may have to supply the > path to sage because the sudo environment likely does not include /opt > in its path) -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
