William Stein wrote:
On Sat, Apr 3, 2010 at 7:56 AM, mhampton <hampto...@gmail.com
<mailto:hampto...@gmail.com>> wrote:
Ok, moving /usr/local/ "fixed" the problem. I wish I knew what I did
that caused it though. I've been building Sage since version 1.4 on
there without problems.
It's sort of totally obvious to point this out, but perhaps you
installed some program, and that program put something in /usr/local/.
Any program can do that upon installation; I think some tex installs may.
I don't know how in OS X to somehow totally hide the existence of
/usr/local/ from a subshell. As root (on Linux at least) one could
easily do so using mount and bind. Making changes to the PATH and other
environment variables is not enough to stop components of Sage looking
in /usr/local during the build, despite .remarks possibly to the
contrary by others in this thread.
-- William
I'd agree with that. In fact, so frustrated with this some times, I've thought
of run 'sed' on the tar source tar file of $package and substituting /usr/local
for /foo/bar.
If the worst came to the worst, and one package in Sage needed that to stop it
looking in /usr/local, although a bit of a drastic measure, it would be a
possibility. It is probably a better solution than requiring a user to be root
to build Sage.
Dave
--
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
URL: http://www.sagemath.org
To unsubscribe, reply using "remove me" as the subject.
