On Mon, 18 Feb 2008, James E Keenan wrote:
> Andy Dougherty wrote:
>
> > The problem here looks relatively simple: The symbol _Parrot_conv_i2_i
> > is defined in two places: myops_ops.o and
> > /usr/local/lib/libparrot.dylib(core_ops.o)
> > That '/usr/local/lib/libparrot.dylib' shouldn't be there. It's probably a
> > remnant of an old installation. Uninstalling the old libparrot should fix
> > this problem.
> Assuming someone needed to do this uninstall, what's the best way to do it?
I don't know. In general, if you install something via some sort of
package manager, then it is usually best to use the same package manager
to uninstall. Otherwise, the package manager may get confused. If you
installed by hand (e.g. with parrot's "make reallyinstall", then you have
to uninstall by hand, since parrot doesn't have a 'make uninstall' target.
The original poster mentioned something called 'macports', but I don't
know anything about it.
A simple 'rm /usr/local/lib/libparrot.dylib' will obviously remove the
file in question, but will leave behind any other files installed by
parrot. Other than by looking at file and directory names and timestamps,
I don't know any way to identify "parrot stuff" that might have been
installed at the same time.
--
Andy Dougherty [EMAIL PROTECTED]
