Could this be a UMASK issue?
echo user UMASK is $UMASK
sudo echo root UMASK is $UMASK
On Dec 20, 2010, at 3:47 PM, Ryan Schmidt wrote:
> On Dec 20, 2010, at 12:28, William H. Magill wrote:
>> On Dec 19, 2010, at 11:42 PM, Ryan Schmidt wrote:
>>> On Dec 19, 2010, at 20:01, William H
Presumably there are a variety of projects you use where which you want to use
differs from project to project?
I create project_name.env files in ~/bin where can set the PATH I want for that
project. Then whenever I want to work on that project, I create a new terminal
window and . project_na
I recently did a port selfupdate and am now on MacPorts 1.700. It's
been working fine with other installs.
I'm running 10.4.11 on a PowerPC G4 (Quicksilver)
Today I tried sudo port -v install emacs-app and got a, to me,
bizarre failure. I captured both the output from port -v and the
Recently, when I did the selfupdate (to version 1.6?) on one of my
machines, I got a message saying some stuff may have been left in /
opt/local/var/db/dports... in the move to ...var/macports and I
should take care of it myself.
That message could be a bit clearer -- is it the case that the
I tried sudo port -v install ruby19
Eventually I got this:
cc -dynamic -bundle -undefined suppress -flat_namespace -
o ../../../../.ext/i386-darwin8/json/ext/parser.bundle parser.o
unicode.o -L. -L../../../.. -L. -L/opt/local/lib-lruby1.9 -
lpthread -ldl -lobjc
compiling mathn/complex
m
Yesterday, on my other machine, I did "port upgrade all" when I
should have done "port upgrade installed".
Today I stopped by the machine (867 MHz G4, OS 10.4.11) and it was
still chugging along...
Luckily I'd added "-v" and " | tee logfile" so a "grep -i fetching
logifile" showed it wa
I've just upgraded my sbcl installation.
For some reason, while the system builds and runs nicely, the
documentation does not -- or at least not doc/manual.
Here is the last part of the "sudo port -v sbcl" output:
Documentation:
man /opt/local/var/macports/build/
_opt_local_var_macports_s
