On Jan 13, 2009, at 4:52 PM, Ryan Schmidt wrote:
On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:
On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
It really does look as though your prefix has somehow been set to
/usr/share.
If it is I don't know where.
bash-3.2# env
SHELL=/bin/bash
TERM=xterm-color
USER=root
SUDO_USER=brad
SUDO_UID=501
SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
__CF_USER_TEXT_ENCODING=0x1F5:0:0
PATH=/Users/brad/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/
sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/
bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
I see /usr/share/bin in your PATH.
bash-3.2# cat ~/.profile
bind -x '"\C-p"':'echo $PWD'
PS1='\h: \u\$ '
alias ls='ls -G'
alias tclsh='rlwrap tclsh'
export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/
sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/
bin:$PATH
export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man:
$MANPATH
You should get /usr/share/bin out of that PATH statement.
Also, remove /usr/local/bin and /usr/local/sbin. It is not supported
to have anything installed in the prefix /usr/local while using
MacPorts; it causes problems for many ports. You should remove any
software in /usr/local/{bin,include,lib,man,share} and install it
using MacPorts instead. (Any other prefix, including any
subdirectory of /usr/local, is fine; it's just /usr/local itself
that's problematic. So there's no problem with keeping /usr/local/
php5/bin or /usr/local/mysql/bin in the PATH. Though php5 and mysql5
are of course available through MacPorts as well.)
Macports versions and variants of mysql and php do not get me what I
need.
The use of /usr/local is so prevalent I'm surprised to hear that I
should not use /usr/local and macports at the same time. Seems
everything I build on freebsd using freebsd ports installs there to /
usr/local. Most unix software that isn't available using macports
installs to /usr/local.
If a macports package want's to use something outside /opt/local that
is available and fit's the need I think that's fine.
Is it possible to keep macports file writes confined to /opt/local
regardless of where the files it uses to build are located?
Do you have this file on your system which on mine is called called
from /etc/profile?
/usr/libexec/path_helper
This script reads paths to env from /etc/paths.
I don't ever remembering editing it but along with /bin and /usr/bin
was /usr/local/bin.
//brad
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
