/opt/local/bin/identify
This means you installed from MacPorts. I had suggested you install manually so that IM identify or convert will be in /usr/local/bin.
So I am confused how you uninstalled and re-installed. If from MacPorts, then you need to install the delegates using MacPorts as well or IM won't be able to find them.
If you have multiple version of IM installed, now, then you probably are getting things confused and IM may have conflicts.
You probably also will need to have Xcode Tools installed first.
I am not a unix guru or programmer either and have no experience with MacPorts. But I got some help at first from others to do the manual install and then afterwards, just kept doing the same thing. The IM install is easy. But some delegates are hard and each may require something else to be installed before it.
Ghostscript is a complicated one to install on Mac manually. If you install from MacPorts, it may be easier. Here is what I had to do when installing manually.
Key to Install Ghostscript on Mac OS X: Install Ghostscript.Framework
(IM does not recogize the installed ghostscript delegate without the framework)
From Ghostscript docs:
ghostscript-8.61/doc/Make.htm#MacOSX
MacOS X
The unix source distribution (.tar.gz) builds fine on Darwin/MacOS X, albeit without a display device. You can generally just use the Makefile generated by ./configure or macosx.mak as your top-level makefile and get a reasonable default build. This will allow you to use Ghostscript from the command line as a BSD-layer tool to rasterize postscript and pdf to image files, and convert between the high-level formats supported by Ghostscript. See the instructions for the unix build below for details of how to customize this build.
There is also a support for building Ghostscript as a framework. This is a special encapsulated shared library format specific to MacOS X. To build the framework, copy macosx.mak to the top-level directory, rename it to makefile and issue 'make framework' from Terminal.app. This will result in a Ghostscript.framework in the sobin directory. It must be manually copied to /Library/Frameworks/ before applications can use it. You may need to create the Frameworks/ directory on some systems.
So My Install Notes:
1) do normal install
./configure
make
sudo make install
2) Follow instructions above
*copy macosx.mak from src to top level of GS source directory
*rename to Makefile
*make framework
*copy framework from sobin directory of GS source code to /Library/Frameworks
*also copy gsc from sobin directory and put in /usr/local/bin (same place as gs is located), then reboot
3) Rebuild IM as usual.
Also Magick recently wrote in
viewtopic.php?f=1&t=11805
"Do you have Ghostscript installed? ImageMagick can utilize the Ghostscript library at build time if its framework is available, otherwise it uses the 'gs' command line utility to interpret Postscript. Make sure gs is in your execution path or edit delegates.xml and replace 'gs' with the absolute path of the utility, for example, /usr/local/bin/gs."
Note there are two delegates.xml files. One is in the IM source directory. But the one that likely needs editing can be found by:
convert -list delegate | grep Path:
Path: /usr/local/lib/ImageMagick-6.4.3/config/delegates.xml
However, this now is not necessary as installing gsc in /usr/local/bin seems to have done the trick (and rebooting).