2011/8/23 Orion Poplawski <or...@cora.nwra.com>:
> See https://bugzilla.redhat.com/show_bug.cgi?id=719785 for the motivation
>
> The environment module system allows users to modify their environment in a
> predictable way, including setting LD_LIBRARY_PATH. However, this makes it
> possible to break the modulecmd binary by putting an incompatible TCL (or
> other) library earlier in the path. It would be great if modulecmd were made
> impervious to such things, but I don't know the best or acceptable method to
> do this. I'm guessing using rpaths would be the easiest.
>
> Thoughts/suggestions?
Would something like this work?
module ()
{
eval `/lib64/ld-linux-x86-64.so.2 --library-path ''
/usr/bin/modulecmd bash $*`
}
(on a 64bit system; on a 32bit system it would need to use /lib/ld-linux.so.2).
- Thomas
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
