On Mon, Sep 21, 2009 at 8:30 AM, Kay Wanous wrote:
>
> I think we are going to end up just installing on a completely different
> system. The closest I got was to
>
> export LC_ALL=en_US
>
> which allowed me to call r.version and not have it error out, but
> running it from the program now produ
I think we are going to end up just installing on a completely different
system. The closest I got was to
export LC_ALL=en_US
which allowed me to call r.version and not have it error out, but
running it from the program now produces
Unless anyone has any ideas, I think I'm going to give up
Hi Kay,
On Fri, Sep 18, 2009 at 2:49 AM, Kay Wanous wrote:
> Any ideas?
This might not be of any help at all but... If you want to limit the
damage that could be done on your system, you might consider
virtualization tools such as VirtualBox OSE, VMware, etc. instead of
using chroot. I have
I think I've narrowed it down a little bit more. Inside the chroot,
root can run sage with R without errors. Looking at a diff of the
straces, when root runs sage, it opens /usr/lib/locale/locale-archive
but it doesn't if it's run as the sage user:
Root -
brk(0)
