Problems installing ports
jason.debacker at gmail.com
Thu Apr 22 07:44:21 PDT 2010
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 the problem with sed (using verfiy
disk revealed repairs needed, before, but not after reinstalling Snow
Leopard). I then had to reinstall Xcode from the Snow Leopard disk because
I was missing something from the Unix developer tools.
My current road block has to do with .dylib file in usr/local/bin not being
of the right architecture. I read about a solution to this on an
old MacPorts ticket, but have not had a chance to see if it works. Will try
I'll post all my problems and solutions when successful.
On Thu, Apr 22, 2010 at 9:10 AM, LuKreme <kremels at kreme.com> wrote:
> 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 the OP simply needs to install the XCode Developer
> He would not have been able to build MacPorts without the Developer Tools,
> would he? Anyway, sed is a basic part of every OS X install and has nothing
> to do with the developer tools.
> ' I really should talk to him, sir. He's had a near-death experience!' 'We
> do. It's called living.' --Hogfather
> macports-users mailing list
> macports-users at lists.macosforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users