On Tue, Aug 9, 2011 at 1:56 PM, doh123 <wineforum-user@xxxxxxxxxx> wrote: > more info would help... > > why it is in /usr/local ... did you do a build by hand? /opt/local is where Macports puts everything. How exactly did you get > Wine and how are oyu changing things? Its not going to run somewhere differently than the "which" command shows, > because that pulls from the same path... unless your running in different terminal sessions that have different $PATH. > doh123: It is possible what is in /usr/local/bin is only a symlink to /opt/local/bin Also, if /opt/local/bin is not in the PATH and before /usr/local/inb then which wine will not find wine installed there. You do have a valid point though, how did Wine get in /usr/local/bin and is there? Is it a symbolic-link to wine somewhere else or is this an actual executible program. Questions that need to answered have been asked: What is at /usr/local/bin/wine (ls -l wine and file wine are two commands that you can use)? What is at /opt/local ? We can provide help if needed, but if your MacPorts installation is broken you may have to go to them for help. Thank you. James
