Re: Problems installing ports

2010-04-23 Thread Ryan Schmidt
On Apr 23, 2010, at 13:08, Jason DeBacker wrote: I was able to sucessfully install qtoctave. I temporarily moved /usr/local then uninstalled and reinstalled macports and finally installed qtoctave through macports and everything worked. It wasn't enough to just move /usr/local and clean

Re: Problems installing ports

2010-04-23 Thread Bradley Giesbrecht
On Apr 22, 2010, at 10:03 AM, Ryan Schmidt wrote: On Apr 22, 2010, at 11:18, Rainer Müller wrote: On 2010-04-22 16:44 , Jason DeBacker wrote: My current road block has to do with .dylib file in usr/local/bin not ^ MacPorts uses

Re: Problems installing ports

2010-04-23 Thread Ryan Schmidt
On Apr 23, 2010, at 15:06, Bradley Giesbrecht wrote: On Apr 22, 2010, at 10:03 AM, Ryan Schmidt wrote: What he means is: MacPorts is in /opt/local, and anything in /usr/local is something you've installed locally on your system and it might interfere with MacPorts, therefore it is not

Re: Problems installing ports

2010-04-22 Thread LuKreme
On 21-Apr-2010, at 10:52, Joost Kremers wrote: On Wed, Apr 21, 2010 at 09:10:45AM -0700, Bradley Giesbrecht wrote: If I were you and I didn't understand why /usr/bin/sed and /usr/bin/ uname I would start by trying to understand why they disappeared if they ever existed. Could it be that

Re: Problems installing ports

2010-04-22 Thread Jason DeBacker
Thanks for all the help. I have still not successfully installed qtoctave, but I'm at least getting closer. Not sure why, but sed was in usr/local/bin not usr/bin. I copied and moved it to usr/bin, but it was for the wrong architeture (I have i386). I installed Snow Leopard again and got past

Re: Problems installing ports

2010-04-22 Thread Rainer Müller
On 2010-04-22 16:44 , Jason DeBacker wrote: My current road block has to do with .dylib file in usr/local/bin not ^ MacPorts uses /opt/local by default and it is strongly recommended not to use /usr/local.

Re: Problems installing ports

2010-04-22 Thread Ryan Schmidt
On Apr 22, 2010, at 11:18, Rainer Müller wrote: On 2010-04-22 16:44 , Jason DeBacker wrote: My current road block has to do with .dylib file in usr/local/bin not ^ MacPorts uses /opt/local by default and it is strongly

Re: Problems installing ports

2010-04-21 Thread Bradley Giesbrecht
On Apr 21, 2010, at 7:53 AM, Joshua Root wrote: On 2010-4-22 00:43 , Jason DeBacker wrote: I was able to install MacPorts 1.8.2 without any error messages, however when I try to install a program via the sudo port install command, I run into the error sed: command not found.

Re: Problems installing ports

2010-04-21 Thread Joshua Root
On 2010-4-22 01:00 , Bradley Giesbrecht wrote: On Apr 21, 2010, at 7:53 AM, Joshua Root wrote: On 2010-4-22 00:43 , Jason DeBacker wrote: I was able to install MacPorts 1.8.2 without any error messages, however when I try to install a program via the sudo port install command, I run into

Re: Problems installing ports

2010-04-21 Thread Jason DeBacker
/usr/bin/sed is a standard part of Mac OS X. I don't know how it was deleted on your system, but you'll need to get it back. This usually means that your /usr/bin/uname command (also a standard part of OS X) is missing or malfunctioning. Do I need to completely reinstall OS X to get

Re: Problems installing ports

2010-04-21 Thread Bradley Giesbrecht
On Apr 21, 2010, at 8:50 AM, Jason DeBacker wrote: /usr/bin/sed is a standard part of Mac OS X. I don't know how it was deleted on your system, but you'll need to get it back. This usually means that your /usr/bin/uname command (also a standard part of OS X) is missing or malfunctioning.

Re: Problems installing ports

2010-04-21 Thread Joost Kremers
On Wed, Apr 21, 2010 at 09:10:45AM -0700, Bradley Giesbrecht wrote: If I were you and I didn't understand why /usr/bin/sed and /usr/bin/ uname I would start by trying to understand why they disappeared if they ever existed. Could it be that the OP simply needs to install the XCode Developer

Re: Problems installing ports

2010-04-21 Thread Ryan Schmidt
On Apr 21, 2010, at 11:52, Joost Kremers wrote: On Wed, Apr 21, 2010 at 09:10:45AM -0700, Bradley Giesbrecht wrote: If I were you and I didn't understand why /usr/bin/sed and /usr/bin/ uname I would start by trying to understand why they disappeared if they ever existed. Could it be that