Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm an absolute terminal noob (the wine installation process was my first ever time opening it) so its probably a simple fix. that being said I will need any answer broken down to its simplest possible components, I'm a proficient copy-paster :P

I am trying to instal wine on my macbook with snow leopard, I've been following an online tutorial and installed mac ports, a java package, and xcode. however when comes to the actual installation of wine, this happens:

bogon:~ Chris$  sudo port install wine
sudo: port: command not found
bogon:~ Chris$ 

Based on my research the problem has something to do with configuring xcode properly. If you agree that this is the likely culprit, could someone please break down just how to that, something to do with my profile or something like that (did I mention I'm a noob :P)

share|improve this question
Use WineBottler instead. The first Google hit is not necessarily the best for everyone. – Daniel Beck Apr 2 '11 at 4:45

Actually, your problem is more likely that /opt/local/bin isn't in your (or root's) $PATH, which will happen if you are using a Terminal window that was open when you installed MacPorts or if you overrode its attempt to add $PATH to your shell configuration. If there are XCode issues, you won't find out about them until you can run port.

EDIT: per comments, this appears to be a missing tclsh. On my Snow Leopard system, its vitals:

mress:10078 Z$ ls -l /usr/bin/tclsh
lrwxr-xr-x  1 root  wheel  8 Nov 19  2009 /usr/bin/tclsh@ -> tclsh8.5
mress:10079 Z$ ls -lL /usr/bin/tclsh
-rwxr-xr-x  1 root  wheel  42640 Jul 23  2009 /usr/bin/tclsh*
mress:10080 Z$ pkgutil --file-info /usr/bin/tclsh
volume: /
path: /usr/bin/tclsh

install-time: 1258693096
uid: 0
gid: 0
mode: 755
share|improve this answer
Well, I'm using a new terminal window, have tried several times, even after a restart. And I haven't overrode anything as far as I know (don't know how to do that - and by extension whether or not I have). I've been following this to the dot, and everything was going smoothly until 'part 3', when the above mentioned error happened. Thanks for the quick reply btw – Chris Apr 2 '11 at 4:59
So what does echo $PATH return? Does it include /opt/local/bin? If not, you'll need to add that to ~/.bash_profile (see for details). Interestingly, I see that notes problems with the installer updating the wrong startup file, which could also lead to this. – geekosaur Apr 2 '11 at 5:04
this is what it returns:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/‌​bin:/usr/X11/bin – Chris Apr 2 '11 at 5:13
so it seems to me that /opt/local/bin is there, does that mean its a problem with the installer updating the wrong startup file? – Chris Apr 2 '11 at 5:16
No, that suggests something else is wrong. Does /opt/local/bin/port exist? If so, what happens if you run it by full path? (Conceivably the system might not be finding Tcl to interpret the script for some reason, although tcl should be included in OSX.) – geekosaur Apr 2 '11 at 5:19

Late, but if anyone else needs it. First do "sudo port"

second "sync" when ports tree is updated "install wine"

Hope it helps

share|improve this answer
that didn't work but this did: sudo port -d selfupdate – circuitry Dec 10 '15 at 5:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .