[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-smalltalk] What might cause "No runnable processAbort trap"?

From: Duke Normandin
Subject: Re: [Help-smalltalk] What might cause "No runnable processAbort trap"?
Date: Thu, 7 Jan 2010 06:16:15 -0700 (MST)
User-agent: Alpine 2.01 (OSX 1266 2009-07-14)

On Thu, 7 Jan 2010, Paolo Bonzini wrote:

> > Choking on a bone in libtool, but why?
> Hmm, sounds like a hosed libtool installation, see also
> Try removing _any_ you have in the checked-out tree, and
> then do "autoreconf -fvi" and recompile.


> Maybe it could also because of MacPorts vs. /usr/bin.  Did I mention
> I hate MacPorts?  However, the above seems more likely...

You and me both! Why could they not "leave well enough" alone? I've
got crap in /sw/local/blah from "fink"; crap in /opt/blah from
MacPorts; and the usual stuff in /usr/blah where it's suppose to
go. It's enough to piss off a Pope... ;)


dnormandin@ ~
05:50 am >> port installed libtool
The following ports are currently installed:
  libtool @2.2.6a_0 (active)
dnormandin@ ~
05:50 am >> port location libtool
Port libtool 2.2.6a_0 is installed as an image in:
dnormandin@ ~
05:52 am >> ls -AF /opt/local/var/macports/software/libtool/2.2.6a_0

So libtools is living in /opt/blah. You want them in the /usr/ tree? I
wonder how many files we're talking about here? I could symlink them
to /opt/whatever, but what a &address@hidden PITA! Can't we do something in the
"configure" script or the "Makefile", line "ifdef $OSTYPE or
something, then look at /usr then /opt?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]